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
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
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
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
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
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
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

Aug 7, 2018 · 9:39 AM UTC

1
2
2
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