Joining the existing packaged #WebIDL extracted from web specs, please meet the just-released packaged definitions of #CSS properties and values npmjs.com/package/@webref/cs…
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… 🎉🎇
If the charter is approved, this new Working Group would focus on standardizing the Web Neural Network (#WebNN) API, a set of low level computing primitives to run #MachineLearning models efficiently in browsers - github.com/webmachinelearnin…
The conclusions from the workshop include proposed work on a Machine Learning Working Group to standardize the Web Neural Network API → github.com/w3c/machine-learn…
The Service Workers Working Group develops the … #ServiceWorker specifications, the cornerstone of #PWA - this charter is also the first one where a group is set to use the eternal Candidate Recommendation mode of Living Standards à la W3C w3c.github.io/charter-drafts…
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
2) scheduler.postTask() would allow to classify tasks in the priority queue based on 3 levels: user-blocking, user-visible and background. github.com/WICG/scheduling-a…
1) scheduler.yield() would allow to run higher-priority tasks without yielding to same-priority tasks, something not possible with current #APIs and which tend to discourage script from yielding, leading to overall reduced responsiveness github.com/WICG/scheduling-a…