CSS Properties & Values API: Cascade must not be affected |
|||
Issue descriptionHow cascading works w.r.t. registered custom properties has changed recently ( https://github.com/w3c/css-houdini-drafts/commit/8dfc2d985618a23f97e05c42f7ef6b083ef3256d ). I'm pretty sure we throw out syntax-incorrect values during parsing if the property is registered, which is now the wrong behavior.
,
Jul 5
,
Jul 30
Nope. We do it correctly. Added a WPT test for the new behavior. https://chromium-review.googlesource.com/c/chromium/src/+/1136448 |
|||
►
Sign in to add a comment |
|||
Comment 1 by andruud@chromium.org
, Jul 4Blocking: 641877