Get involved in @w3c and give input on all of our specs. See also youtube.com/@W3COfficial and @w3cdevs@w3c.social. By @dontcallmeDOM and @marieforgue
Joined October 2014
- Tweets 4,375
- Following 608
- Followers 11,339
- Likes 2,472
W3C Developers (@w3cdevs@w3c.social) retweeted
Spec maintenance is perhaps not the most glorified part of standards dev while at the same time it is hugely important to ensure the web platform remains consistent and interoperable as it evolves. In this particular case the trigger was alignment with the WebIDL spec evolution.
The new charter for the Devices and Sensors Working Group adds maintenance of the existing Geolocation API (navigator.getCurrentPosition()) to its existing scope w3.org/2019/02/DeviceAPIChar…
1
1
14
They are also developing a new Geolocation API based on the Generic sensor framework
This new Geolocation API is designed to provide similar features to the well-known navigator.geolocation.getCurrentPosition() API but with a model aligned with the Generic Sensor API framework.
For input and contributions, head to the github repo github.com/w3c/geolocation-s…
1
That group is already responsible for the maintenance of the Device Orientation API, which has recently got renewed attention in a tension between mitigation of privacy concerns & backwards compatibility
📢 The Web is abuzz about new Safari privacy settings: theverge.com/2019/2/5/182118… 💡 Meanwhile W3C group is engineering a privacy-preserving solution to keep motion-based web experiences from breaking: github.com/w3c/deviceorienta… Proud to lead this group that acts w/ a sense of urgency.
1
2
The new charter for the Devices and Sensors Working Group adds maintenance of the existing Geolocation API (navigator.getCurrentPosition()) to its existing scope w3.org/2019/02/DeviceAPIChar…
This tweet is unavailable
2
1
1
1
Also, impressive report on the progress accomplished in 2018, with more goodness expected in 2019
MDN saw many important changes in 2018! We added interactive examples, we updated our web compatibility tables, and more.
If you're curious about the people behind our MDN project, read @jwhitlock's recent @mozhacks post: hacks.mozilla.org/2019/01/md…
1
Among the highlights of the meeting from a @w3cdevs perspective: an upcoming Web developer survey to identify gaps and needs in the Web platform, a cross-browser dev conference in 2019, and solid plans for increasing interactions between docs & standardization
1
The MDN Product Advisory Board recently met in #NYC - the minutes of the meeting are available in their github repo github.com/mdn/pab/blob/mast…
Spending the next two days with the @MozDevNet product advisory board. @dontcallmeDOM @jorydotcom @alispivak @atopal @patrickkettner @robertnyman @chrisdavidmills @MegginKearney: good people who are trying to help make MDN an even better cross-browser resource for web developers.
1
1
In this talk, @alispivak shares some of the history of @MozDevNet and how the Product Advisory Board (PAB) started end of 2017 is helping to better create the documentation developers want and need.
Among the many the exciting projects @mozdevnet is pushing and the PAB is tracking, most relevant for @w3cdevs is a push to make Web documentation a channel for input & feedback to standardization - lots of ideas toward that in our issue tracker github.com/mdn/pab/issues?q=…
1
Another video from our #w3cdevs2018 meetup last October in #Lyon: @alispivak presents @MozDevNet and its intersections with @w3c standardization vimeo.com/312902015
1
1
3
W3C Developers (@w3cdevs@w3c.social) retweeted
Engaging in Web Standards—The “Compatible with Most Web Developers” Approach by @tomayac:
👉 medium.com/dev-channel/engag…
Whether it's in the @w3c, @wicg_, or @TC39, regular Web developers whose day job isn't standards should not be afraid to engage and make their voice heard! 👂
4
23
3
61
in a little more than an hour ⌚️…
Whether you're new to digital #accessibility or a seasoned #w3c #ux #a11y professional who wants to share info with others, hope you'll join us today, Tuesday 5 February @ 12 noon Eastern!
Register: zoom.us/webinar/register/111…
W3C Developers (@w3cdevs@w3c.social) retweeted
The possibilities for eCommerce are, I hope, self-evident. So much potential for mixed reality for large parts of the @gs1 community. Alibaba, Amazon, Google - they're all there w3.org/2000/09/dbwg/details?…
Today, the #ImmersiveWeb Working Group released its first official draft of #WebXR Device #API. WebXR is the successor to #WebVR, as @Lady_Ada_King explains in the third and last part of her interview on Web & XR (virtual + augmented reality) vimeo.com/313372258
3
Thanks again to @Lady_Ada_King for sharing the vision behind the #ImmersiveWeb in this 3-part video series! vimeo.com/313372258
2
The @w3c #ImmersiveWeb #WorkingGroup was meeting in California last week, with lots of progress made around the management of input controllers, hit testing for #AR and much more, to be brought to the specification in the upcoming few weeks
Woooo! Real-world hit testing has now been merged into the #WebXR spec! There ain't no party like an AR party!
1
1
The WebXR spec is developed on #github where you should go to bring feedback on the #API github.com/immersive-web/web…
1
1
The best way to play with #WebXR at the moment is through the WebVR-based #polyfill github.com/immersive-web/web…
1
1
With this First Public Working Draft, #WebXR Device API starts its path on the standardization track, aiming to become a @w3c #WebStandard w3.org/TR/2019/WD-webxr-2019…
This tweet is unavailable
1
1
#WebXR is set to replace #WebVR: it provides better integration with the rest of the Web platform, and a much firmer ground for Augmented Reality #AR in addition to Virtual Reality #VR
The #WebXR Device API brings the right primitives to create VR & AR experiences in Web browsers: connecting to VR headsets, setting up the right rendering path, support for the right input devices, etc
1
1