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
To help keep track of this flurry of ideas, we're proposing to share info _here_ on these early proposals as they get adopted by these groups. Let us know with a ♥ if you think that's useful!
1
1
Prior to being taken up in @w3c formal standardization process, many future #WebPlatform features start as ideas discussed in #W3CCommunityGroups. One of these, the Web Incubator @wicg_ , is a notable hub for incubating these proposals. #WebPlatformEvolution
1
1
2
23 Feb.: hybrid event in partnership with the Australia Western Region #W3Chapter with #w3c speakers @shawn_slh @BillKasdorf and Joshue O’Connor #a11y #WCAG #XR a11yperth.com/events/pwac-20…
1/2 We are so excited about our speakers for this year's PWAC! Tune in all week for bios on each speaker and find out what they'll be talking about on Feb 23rd! Don't forget to grab your PWAC tickets at: events.humanitix.com/perth-w…
3
4
W3C Developers (@w3cdevs@w3c.social) retweeted
Third @w3c Games Community Group meetup was all about runtimes and webviews - talks from Alicia Nie (Tencent), Andre Bandarra (Google), and Jacob Clark (BBC). coil.com/p/end3r/W3C-Games-C… #gamedev #HTML5 #JavaScript #W3C #community #meetup
8
1
W3C Developers (@w3cdevs@w3c.social) retweeted
And @MiriSuzanne is going to talk all about it at @webdirections hover Webdirections.org/hover
3
1
11
W3C Developers (@w3cdevs@w3c.social) retweeted
It means we’re finally getting container queries. This will enable components that can be placed in any context and work. A whole new era of responsive design.
4
9
1
37
W3C Developers (@w3cdevs@w3c.social) retweeted
Check it out! All the web platform’s IDL with duplicate and broken stuff fixed, so that it all makes sense together. I’m using this to generate feature detection tests for MDN’s browser-compat-data: mdn-bcd-collector.appspot.co… Probably useful for other tools too, let us know if so!
Specs defining browser #APIs use a formal definition language (#WebIDL) which helps with writing and implementing these APIs. @tidoust, @dontcallmeDOM and @foolip are making it easier to re-use these definitions through a newly released NPM package: npmjs.com/package/@webref/id… 🎉🎇
2
4
This proposed charter would (re-)create a Math Working Group to refresh the support of #MathML in browsers w3c.github.io/charter-drafts…
This tweet is unavailable
1
4
3
13
To learn more about these projects and how that data gets reused (e.g. to document browser compat data in @MozDevNet), watch the presentation given during #w3cTPAC last October: youtube.com/r9AXrFoFEg4 (slides at w3.org/2020/Talks/TPAC/uncon…)
1
NPM packages the IDL pieces, with more packages (e.g. for #CSS definitions) in the pipe
1
2
Features such as 'all', 'initial' and 'unset' are now a proven standard and join the list of other specs incl. "Selectors Level 3", "Fonts Level 3" and "Writing Modes Level 3" - see the current state of #CSS in the latest CSS Snapshot 2020 by the @csswg w3.org/TR/CSS/
1
1
Congrats to editors @fantasai and @tabatkins for the newly published #WebStandard "#CSS Cascading and Inheritance Level 3" w3.org/TR/css-cascade-3/ #timetoadopt
This tweet is unavailable
1
2
2
5
W3C Developers (@w3cdevs@w3c.social) retweeted
I was in an interesting meeting today around the W3C process so I want to do a threaded poll to get your thoughts. Please RT for reach. *NO SEARCHING* At which point in the W3C process should a user-agent (eg: browser vendor) consider implementing the proposal?
11% Editor's draft
38% Working Draft
37% Proposed Recommendation
14% Recommendation
736 votes • Final results
8
43
2
18