-
Notifications
You must be signed in to change notification settings - Fork 12
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
Contact Picker API #97
Comments
I recently got an update that the Contact Picker API is being implemented in WebKit:
The group should reconsider adopting this specification from the WICG. |
That's exciting to see! Yeah, the group should pick this up then. |
Given this agreement what are the next steps? As I understand it adopting this API requires rechartering since it wasn't listed as a potential deliverable like Fold Angle was. CC @xfq |
Per https://www.w3.org/2020/11/das-wg-charter.html#add-new we prepare an updated Charter that differs only in deliverables. Also @plehegar should be able to assist. |
Are there other browsers that have implemented, are implementing, or plan to implement this spec? |
The next step is to go through the rechartering process (add it to the draft charter, ask for horizontal/management/AC review etc.). We can also organize a meeting before that to see if the WG has any ideas or suggestions. |
I poked the Mozilla folks about it to see if they might consider it "worth prototyping". |
The Devices and Sensors Working Group just discussed Contact Picker API, and agreed to start the process to add Contact Picker API to the DAS WG Charter: https://www.w3.org/2021/04/06-dap-minutes.html#t01 |
Per discussions in w3c/strategy#267 , we will make the Contacts Picker API a joint deliverable between WebApps and DAS. |
Addressed by https://www.w3.org/2022/11/das-wg-charter.html |
Making a note here that https://wicg.github.io/contact-api/spec/ might advance to DAS WG in the future.
The group had Contacts API in its charter 2009-2016, and the current Contact Picker API proposal could be characterized as a web-friendly subset of that API.
@reillyeon @marcoscaceres
The text was updated successfully, but these errors were encountered: