New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CSS Houdini #93

flaki opened this Issue Jun 21, 2018 · 1 comment


None yet
3 participants

flaki commented Jun 21, 2018

Request for Mozilla Position on an Emerging Web Specification

Other information

Under consideration: Worklets Level 1, CSS Paint API Level 1, CSS Layout API Level 1
Currently being implemented: CSS Typed OM Level 1, CSS Properties and Values API Level 1
— according to the Mozilla Wiki on DOM/Houdini

“Worklets is one of the Houdini specs we are "considering" but have no firm implementation plans for. Unlikely for 2018, we can reconsider when doing 2019 CSS priorities.”
Tantek Çelik, bugzilla bug #1315239

With Chrome's shipped Paint API and partial implementations of other APIs, coupled various, spec-compliant polyfills appearing developer interest seems to be on the rise, with almost all JavaScript/Web-related conferences sporting a talk on the lineup about the magical developer-facing features, and encouraging the audience to start experimenting. Browser support, of course, always comes up (and never fails to chill the excitement of the talk presented), and although @surma's implementation tracker does a good job in summarizing the (current and expected) support of various browsers, a clear cut decision/expectation on various parts of the Houdini family features would be still very useful.


This comment has been minimized.


tantek commented Jun 21, 2018

Mozilla has been participating in the design and development discussions of Houdini at the CSS Working Group since the beginning and continues to do so.

For Houdini as a whole ("CSS Houdini family features" that have published drafts per this issue), I think the most accurate current summary position is "worth prototyping".

As individual Houdini specifications technically mature (with web developer feedback & iteration) and assuming we see broader use-cases across the web, we can consider stating upgraded positions for each individual specification as appropriate, taking into account the importance of other web platform features.

If anyone has concerns about particular Houdini drafts that should block an explicit "worth prototyping" position, please speak up and we can use "under consideration" while we file issues on those drafts and iterate accordingly.

In addition, since <> ’s tracker was mentioned, this overall Houdini position should not be taken to apply to anything that is not yet at least a published working draft.

If an explicit position is desired for proposals in <> without a working draft, please file separate issues for those.

(Originally published at:

@dbaron dbaron added the w3c label Aug 9, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment