New issue
Advanced search Search tips

Issue 860301 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Jul 30
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 641877



Sign in to add a comment

CSS Properties & Values API: Cascade must not be affected

Project Member Reported by andruud@chromium.org, Jul 4

Issue description

How 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.
 
Blockedon: -641877
Blocking: 641877
Components: Blink>CSS
Status: WontFix (was: Started)
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