Implement CSS.registerProperty API
Categories
(Core :: CSS Parsing and Computation, enhancement)
Tracking
()
People
(Reporter: dholbert, Unassigned)
References
(Blocks 1 open bug)
Details
(Keywords: dev-doc-needed)
Filing this bug to track the CSS.registerProperty API from https://drafts.css-houdini.org/css-properties-values-api/#at-property-rule , to define custom CSS properties.
(We have some prototype patches against older mozilla-central in bug 1273706 and bug 1370344; probably worth starting fresh with a new bug at this point, though, with the old bug as a reference & possibly to track any additional pieces for the full spec.)
|
Reporter | |
Comment 1•2 years ago
|
||
(I imagine the implementation here will proceed alongside an impl in bug 1684605, possibly with one building off of the other.)
|
||
Updated•2 years ago
|
|
||
Comment 2•1 year ago
|
||
Looks like this was implemented in Bug 1840476 , currently under the layout.css.properties-and-values.enabled pref.
Should this bug be closed ?
|
||
Comment 3•1 year ago
|
||
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #2)
Looks like this was implemented in Bug 1840476 , currently under the
layout.css.properties-and-values.enabledpref.
Should this bug be closed ?
Sorry for the late response, there is still more to do before https://wpt.fyi/results/css/css-properties-values-api/at-property.html passes. Further bugs will probably be opened under bug 1273706 instead of bug 1821552, but until those bugs are created, it seems useful to keep bug 1821552 open so we don't lose track of the fact that there is more to do.
|
||
Comment 4•1 year ago
|
||
(In reply to Zach Hoffman [:zrhoffman] from comment #3)
(In reply to Nicolas Chevobbe [:nchevobbe] from comment #2)
Looks like this was implemented in Bug 1840476 , currently under the
layout.css.properties-and-values.enabledpref.
Should this bug be closed ?Sorry for the late response, there is still more to do before https://wpt.fyi/results/css/css-properties-values-api/at-property.html passes. Further bugs will probably be opened under bug 1273706 instead of bug 1821552, but until those bugs are created, it seems useful to keep bug 1821552 open so we don't lose track of the fact that there is more to do.
I think more TODOs have been opened under bug 1273706, so let's close this one.
Description
•