Worklets are a lower-cost way of running code very efficiently as part of the various rendering pipelines of the browser (e.g. while painting, laying out, animating or playing audio) developer.mozilla.org/en-US/…
developers.google.com/web/up… worklets are gonna be a gamechanger.
1
3
1
5
The concept is defined in the Worklets spec, jointly developed by the @csswg and the @w3ctag drafts.css-houdini.org/workl… - repo at github.com/w3c/css-houdini-d…
1
They were developed as part of an effort making various CSS concepts easier to experiment with and polyfill for, known as the Houdini Task Force drafts.css-houdini.org/.
Part of the idea is that it enables anyone to create their own CSS property and values.
Feb 12, 2018 · 3:34 PM UTC
1
Worklets are designed to run code with a very limited scope, and so are made available with a by-design very restricted API surface.
Each type of rendering gets its own dedicated API surface, encompassed in a given WorkletScope.
1
1
The currently defined Worklet scopes are:
* for CSS painting, drafts.css-houdini.org/css-p…
* for CSS layout, drafts.css-houdini.org/css-l…
* for Animations, wicg.github.io/animation-wor…
* for Audio webaudio.github.io/web-audio…
1
1
3
The current known implementations and implementation plans are tracked at ishoudinireadyyet.com/
This is still early days, but it does feel like a pretty big game changer in opening up the browser black boxes!
1