ποΈ January@w3c events - happy new year! ππ
10-11 Jan.: register for π before 5 Jan. (tomorrow!) to attend the online "#AI and #accessibility Research Symposium" @wai
More info at https://www.w3.org/WAI/about/projects/wai-coop/symposium2/
https://twitter.com/w3cdevs/status/1610608799676522502
18-20 Jan.: @dontcallmeDOM participates in a joint @OpenWebDocs/@MDN/@w3c #devrel meeting
https://twitter.com/w3cdevs/status/1610608807096246272
Typical use cases are managing, coordinating and syncing multi-tab interactions. This specification is already largely implemented by modern Web browsers: https://caniuse.com/mdn-api_lock
The Web Locks #API allows scripts to asynchronously acquire a lock over a resource, hold it while work is performed, then release it. Within a #WebApp, it helps coordinate the usage of resources #FPWD #timetogiveinput
https://www.w3.org/TR/web-locks/ https://twitter.com/w3c/status/1610927757243961344
https://twitter.com/w3cdevs/status/1610965096498450433
Feedback is welcome in the spec's #GitHub repo: https://github.com/w3c/web-locks/issues/
https://twitter.com/w3cdevs/status/1610965104966737920
Check also the explainer: https://github.com/w3c/web-locks/blob/main/EXPLAINER.md
https://twitter.com/w3cdevs/status/1610965101116522498
Wrt #privacy, this API is only avail. from a secure top-level browsing context and considers the sensitivity and privacy of contact data. Additionally, a user gesture is needed to initiate the API. Read more about the Contact Picker API concepts and usage: https://developer.mozilla.org/en-US/docs/Web/API/Contact_Picker_API
The Contact Picker #API brings easy access to contacts for #WebApps. It gives one-off access to a userβs contact information with full control over the shared data #timetogiveinput #FPWD https://www.w3.org/TR/contact-picker-1/ https://twitter.com/w3c/status/1605103631887486977
https://twitter.com/w3cdevs/status/1610999259305746433
The Devices and Sensors #WorkingGroup and Web Applications #WorkingGroup welcome feedback in the related #GitHub repo: https://github.com/w3c/contact-picker/issues
https://twitter.com/w3cdevs/status/1610999263143534592
The API is available in #Chrome on Android, and behind a flag in #Safari on iOS. Try this Contact Picker API demo: https://contact-picker.glitch.me/
https://twitter.com/w3cdevs/status/1610999261281357824
Congrats to to Qing An (@AlibabaGroup), @t (@mozilla), @fantasai (#W3CInvitedExpert) and @chaals (@ConsenSys) πππ https://twitter.com/w3c/status/1615351977277378562
These newly elected @ab participants join the continuing ones: @hjrchung (@Samsung), Wei Ding (@Huawei), Tatsuya Igarashi (@Sony), @frivoal (#W3CInvitedExpert), Avneesh Singh (@DAISYConsortium), @TzviyaSiegman (@WileyGlobal) and @cwilso (@Google).
https://twitter.com/w3cdevs/status/1615395902252023808
The @ab's priorities in year 2023 are listed in https://www.w3.org/wiki/AB/2023_Priorities
https://twitter.com/w3cdevs/status/1615395908786753537
The #WebTransport Working Group develops #APIs allowing #WebApps to establish interactive, bidirectional, multiplexed network connections.
Read more in the explainer: https://github.com/w3c/webtransport/blob/main/explainer.md and contribute to the group! https://github.com/w3c/webtransport/blob/main/explainer.md https://twitter.com/w3c/status/1615663825361027072
https://twitter.com/w3cdevs/status/1615729642895196162
ποΈ SAVE THE DATE! This year, an hybrid #w3cTPAC will be held in #Sevilla πͺπΈ, 11-15 Sept. 2023. Along with a @w3c #developers #meetup where we'll propose a great line of speakers, as usual ... π
In the meantime, (re)watch the #w3cdevs2022 technical talks: https://www.w3.org/2022/09/meetup/ (with slides and transcripts)
https://twitter.com/w3cdevs/status/1617839822730854401