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
So if you have great use cases that justify more implementations of the API, follow the links to the various browser bug reports/feature request:
@firefox bugzilla.mozilla.org/show_bu…
@MSEdgeDev wpdev.uservoice.com/forums/2…
@webkit bugs.webkit.org/show_bug.cgi…
But we need more confirmed interests from browser vendors before going there… So far, it is only available in Chromium-based browsers caniuse.com/#feat=web-blueto…
1
1
There was discussions in bringing this work to the formal standardization track as part of the Device and Sensors Working Group a few months ago github.com/w3c/dap-charter/i…
1
It is developed in the Github repo at github.com/WebBluetoothCG/we… and discussed in the mailing list archived at lists.w3.org/Archives/Public…
1
The API enables connecting to and interacting with Bluetooth LE devices in Web browsers, providing low friction way to deploy apps for many BLE-based connected objects. webbluetoothcg.github.io/web…
1
As reported in this very good overview of Web Bluetooth, this API is right now in pre-standardization in the Web Bluetooth Community Group under the lead of @jyasskin w3.org/community/web-bluetoo…
Web Bluetooth is important and developers should know about it. Learn more from @bluetooth_mdwrx: bit.ly/2DmhUpn #IoT #dev #IIoT
1
1
2
Great recap of past, ongoing and emerging work on the Web media stack, including a link to Web Media Roadmap which has all the details you might need in that space w3c.github.io/web-roadmaps/m…
(that roadmap as you've guessed is itself maintained on github github.com/w3c/web-roadmaps/ )
This tweet is unavailable
2
The spec is developed (along with most other @csswg specs) in the repo at github.com/w3c/csswg-drafts/ and is edited by the oh-so-ever-productive @fantasai @cssrossen @tabatkins
2
5
The main addition to the current CSS Grid Layout Level 1 is subgrids - @meyerweb described the concept excitedly a couple of years ago meyerweb.com/eric/thoughts/2…
There were initially part of the Level 1 spec, but had to be postponed to find the right approach for implementability.
2
3
10
CSS Grid Layout has taken the world of CSS design by fire over the past year, thanks in part to the great outreach around it (notably by @jensimmons and @rachelandrew ).
The @csswg has now published the first draft of the new level of CSS Grid w3.org/TR/2018/WD-css-grid-2…
This tweet is unavailable
1
5
18
最近公開されたWeb標準の @w3c HTML5 Media Captureの日本語翻訳が利用可能になりました：asahi-net.or.jp/~ax2s-kmtn/i… どうもありがとう @omnidirect!
1
Their work is ongoing on github github.com/gpuweb/gpuweb with records of their day-to-day work in the wiki github.com/gpuweb/gpuweb/wik…
The technical work there is not for the faint of heart, though - beware!
Compared to #WebGL, it aims at being more “web-by”, lower level for greater performance, mappable to more platforms, and applicable both to graphic and computational use cases (e.g. maching learning). gpuweb.github.io/admin/cg-ch…
1
1
Right now, that accessibility tree is not exposed directly to developers (although it is directly influenced by the DOM); there is an ongoing exploration to exposing it in an Accessibility Object Model proposal wicg.github.io/aom/explainer… - developed on github github.com/wicg/aom
2
1
7
.@tink gave a nice introduction to the topic at one of our previous #w3cTPAC meetups, and you can watch and listen a similar talk of her from a couple of years ago youtube.com/watch?v=qi0tY60H…
1
1
The #Accessibility Tree is the model of information that assistive technologies (such as screen readers) use to expose the components of an interface (incl a Web page) to their users.
Now in Chrome 64: Select an element in the DOM Tree, and the new #Accessibility pane shows you that element's position in the accessibility tree, as well as its ARIA attributes and computed properties.
1
15
1
31
@googlechromedev you may want to fix chromestatus.com/feature/667… with regard to safari plans (see thread)
Thanks for the correction - there is indeed an old bug open for it but which seems to indicate it is not really being worked on any more bugs.webkit.org/show_bug.cgi…
2
The new charter mostly sets the group to finish its work w3.org/2014/secondscreen/cha….
It also points to the work of the Second Screen *Community* Group which is incubating work on an interoperable protocol as support for the Presentation API github.com/webscreens/opensc…
1
The Remote Playback API focuses specifically on rendering media content on a remote screen w3.org/TR/remote-playback/
It is available in @googlechrome and in development in @webkit chromestatus.com/feature/577…
The spec is developed in github.com/w3c/remote-playba…
1
1