w3cdevs Twitter archive for November 2019

Follow what participants to the workshop are sharing on the #w3cInclusiveXR hashtag - 1st day was a blast, 2nd day starting a in a few hours. You can also follow the live caption feed of the discussions at https://captionmax.1capapp.com/event/w3c starting 9am PT https://twitter.com/w3cdevs/status/1189910373836771331

Congrats to editors @tabatkins and @frivoal for the newly published @w3c #WebStandard "CSS Containment L1" #timetoadopt https://twitter.com/csswg/status/1197449310335619072

The CSS contain property lets #developers optimize different Web page components' performance, for more efficient rendering/painting. Try it out!

Lots of progress on the standardization front for the ideas raised during the #w3cgames2019 #W3CWorkshop six months ago! Read @tidoust's post: https://www.w3.org/blog/2019/11/status-update-on-web-games-technologies/

Read also the workshop report itself that reflects the discussions on threading support, WebIDL Bindings in #WebAssembly, latency, cloud gaming, #monetization, indie #games, and more:
https://www.w3.org/2018/12/games-workshop/report.html

For additional info, watch the videos of the talks: https://vimeo.com/showcase/6176604

#timetoadopt this important specification that notably make #PWAs work offline! https://www.w3.org/TR/2019/CR-service-workers-1-20191119/ https://twitter.com/w3c/status/1196709736860790784

A service worker is a script that your browser runs in the
background. Acting as a virtual proxy between the #browser and the #network, it caches the assets of a #website and make them available when the user’s device is offline.

In addition to the offline capabilities, #ServiceWorkers handle notifications, perform heavy calculations on a separate thread, and more. It is a powerful tool for Web #developers!

See current browser support https://caniuse.com/#feat=serviceworkers and the #github repo: https://github.com/w3c/ServiceWorker/

This specification defines http://performance.now(), a precise and monotonic clock for Web #apps. It provides the current time in sub-millisecond resolution #security #performance. Check the good browser support: https://caniuse.com/#feat=high-resolution-time

Congrats to editor @igrigorik for the released @w3c #WebStandard "High Resolution Time Level 2" #timetoadopt https://twitter.com/w3c/status/1197428987062079488

Back in 2018, concerns were raised with regard to how the precision in the clock could help mount #Spectre and #Meltdown attacks - the clock resolution was lowered to 5 microseconds to reduce the risks https://www.w3.org/TR/hr-time-2/#clock-resolution
https://twitter.com/w3cdevs/status/969194392945819648

As every year, @w3c is evaluating how the formal process it uses to standardize specifications should evolve to match the needs from the #Web Platform and its communities.

The W3C Process is maintained by the @ab, with most of the work happening in public in the W3C Process Community Group
https://twitter.com/w3cdevs/status/959078458537185281

... the @ab has been building a full proposal on how to adopt the W3C Recommendation track to allow this kind of iteration for our standards: https://www.w3.org/wiki/Process2020

A major focus on the next revision of the process is to enable more continuous evolution of #W3CStandards. Because the stage-based approach to standardization is sometimes a hindrance to groups that need fast iteration for their work, ...

Hear directly from @fantasai and @plhw3org on the motivations and directions for this process evolution in a presentation they gave at our #w3cTPAC meetings last September: https://www.w3.org/2019/09/TPAC/tp-continuous.html (video+transcript+slides).