-
Notifications
You must be signed in to change notification settings - Fork 56
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Agenda discussion for public meeting on 2023-03-16 #360
Comments
#111 |
@hanguokai, added it to the list, but I think this is technically outside the scope of this group's remit. The features and UX around those features are product decisions made by a given browser vendor. For the purposes of specifying a common platform we can discuss APIs, developer expectations, development patterns, etc., but I don't expect that any browser vendor will want to specify aspects of their program policies or store requirements. |
Would it make sense to discuss again about #317 ? It seems there was an agreement on following the declarative approach implemented by Firefox, but we were waiting for some clearer position from Chrome. |
It seems that there was no substantive progress on #317 at the last meeting(2022-12-08). In order to make progress in next meeting, @oliverdunk should ask Chrome's position internally before next meeting. Thanks you. |
Thanks for the callout @hanguokai. I'll try to look in to this. |
APl to integrate extensions with the Credential Management API |
Updated the list to reflect comments up to this point. |
Closing as the meeting will start shortly. |
I am not very good at listening and speaking English, so it is difficult for me to discuss with you in a video conference. But welcome to communicate with me in text form on the issues. |
Please comment on this issue to add topics for our 2023-03-16. The agenda will be finalized two days before the actual meeting and migrated to our meeting notes doc.
Topics
The text was updated successfully, but these errors were encountered: