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
See anything missing? If you know of use cases that cannot be achieved today with #Web #technologies, please start a new topic in the @w3c’s discourse forum discourse.wicg.io/ or raise an issue on the GitHub repository of this document github.com/w3c/web-roadmaps/…
1
And finally, a brand new and awesome feature: the #implementation status displayed in the #MobileWebApps roadmap uses #MDN Browser Compatibility Data as a source of information, and alerts when an implementation may be partial: npmjs.com/package/mdn-browse… @MozDevNet
1
2
2
5) The preload attribute gives limited control over setting priorities for resource downloading. The Priority Hints specification proposes a more fine-grained mechanism: w3.org/2018/07/web-roadmaps/… #WebPerf
1
4) The @csswg is adopting the overscroll-behavior property proposal, which would help #MobileDevelopers create efficient pull-to-refresh and infinite scrolling paradigms: w3.org/2018/07/web-roadmaps/… #WebPerf
1
3) Did you know that you can use the #CSS contain property to optimize DOM rendering? Check out: w3.org/2018/07/web-roadmaps/… #WebPerf
1
1
2) Looking for a way to run scripted animations without impacting the main thread? The #CSS Animation Worklet #API can help: w3.org/2018/07/web-roadmaps/… #WebPerf
1
1) Measuring event latency today requires an event listener, which introduces unnecessary performance overhead. The Event Timing #WebPerf #API proposes a simple and efficient mechanism to measure the latency of events triggered by user interaction: w3.org/2018/07/web-roadmaps/…
1
The summer edition of the #roadmap of #WebApps on Mobile is out! It highlights exploratory work on how @w3c #Web technologies help optimize performance: w3.org/2018/07/web-roadmaps/… #July2018 @tidoust @XueFuqiao @W3CChina
This tweet is unavailable
1
1
The meeting is in the same room as the @w3ctag meeting last week. But THEY did not have a Unicorn 🦄
4
Today and tomorrow, @dontcallmeDOM is participating to the @MozDevNet product advisory board meeting hosted by @MSFTResearch in Seattle 🇺🇸 developer.mozilla.org/en-US/…
2
1
3
”In cases where DOM manipulations would cause jank, this [proposed API] instead allows the user-agent to split up the work across several frames, yielding for script and user interactions. When the updates are finished processing, the result is displayed without jank.”
Locking display updates to HTML elements, so-called Display locking - Very interesting
github.com/chrishtr/display-…
3
3
9
Deadline is fast approaching (4 August - 5pm CEST)! Get funding for your involvement in W3C standards' development. 🤞Good luck to all applicants!
Are you based in #Europe and actively involved in @w3c #WebStandards development? You can apply for funding this work (before August 4): standict.eu/OpenCalls/2nd-Op… @Stand_ICT
2
2
Extension date for the call for participation: 31 July. The program committee already received 47 submissions, so do not hesitate to join the discussion! w3.org/publishing/events/tok…
Interested in presenting at this #manga #publishing @W3CWorkshop? Please submit your interest before 20 July! w3.org/publishing/events/tok… @w3c_keio @Keio_univ_PR 🇯🇵
1
⚠This workshop has been rescheduled to September 26-27 - deadline for expression of interests and position papers is on August 17
Next #W3CWorkshop will be looking at how to manage access to sensitive features in #Web #browsers! w3.org/Privacy/permissions-w… - hosted by @Qualcomm, September 18-19, in #SanDiego, CA 🇺🇸
2nd day minutes have started
Starting day 2 of the @w3ctag face-to-face triaging new issues.
Minutes: cryptpad.w3ctag.org/code/#/1…
And that charter too has now been approved nitter.vloup.ch/w3c/status/10221… w3.org/2018/distributed-trac…
This is a proposal for a brand new Working Group, to develop work in a brand new area for @w3c. Distributed Tracing is to help manage systems deployed in distributed environments (e.g. in #serverless approaches) w3.org/2018/04/distributed-t…
1
You can get a glimpse at to what the future of #WebRTC looks like in our recent thread from the previous #F2Fmeeting of the group
LIVE REPORT! The #WebRTC #WorkingGroup is meeting in #Stockholm 🇸🇪 today and tomorrow. A major focus is to look at the future of #WebRTC: which use cases it should cover, which new #APIs it should expose, and new ways of interacting with it (e.g. in workers)
It took a bit longer than usual, but the new charter for the #WebRTC Working Group has now been approved nitter.vloup.ch/w3c/status/10217… lists.w3.org/Archives/Public…
The group which is defining the #WebRTC #JavaScript APIs is proposing a new charter to map its work for the next couple of years. w3.org/2018/04/webrtc-charte…
#WebRTC enables audio-video communication and #P2P data in browsers.
1
This is tomorrow! Don't miss it if you're in #Seattle 🇺🇸
26: @w3ctag also organizes a #public #meetup "MeetTheTAG". Come learn about current TAG's work (design reviews of emerging #Web technologies github.com/w3ctag/design-rev… ) and give feedback in real time! ti.to/w3c-tag/meet-the-tag-s… #Seattle 🇺🇸
1
2
Naturally, this privacy & security questionnaire itself needs to be maintained, as bugs and gaps get identified github.com/w3ctag/security-q…