Open Bug 2033678 Opened 1 month ago Updated 25 days ago

revert-layer on a custom property as a result of a substitution is not properly dealt with

Categories

(Core :: CSS Parsing and Computation, defect, P3)

Product:
Core
Component:
CSS Parsing and Computation
Version:
Firefox 152
Type:
defect

Tracking

()

People

(Reporter: janeori, Unassigned)

References

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/147.0.0.0 Safari/537.36

Steps to reproduce:

Here is an interop test panel

https://codepen.io/propjockey/pen/WbGWBaQ/e6e29eb80973b7ad5c254009053a4b36?editors=1100

All green in chrome
all red in firefox except for the hardcoded value
mixed results in safari

Thank you!
// Jane

Actual results:

firefox does not resolve computed values of revert-layer as equivalent to the hardcoded revert-layer

Expected results:

the entire test panel provided should be green

Component: Untriaged → CSS Parsing and Computation
Product: Firefox → Core

I believe this is basically bug https://github.com/w3c/csswg-drafts/issues/9131 (but a nicer test-case).

The relevant code is here. I believe we're going to need to rejigger this a bit more. There are some spec changes that are relevant here but which we haven't adopted yet (in particular, make custom property detection not look at fallbacks eagerly, etc).

Status: UNCONFIRMED → NEW
Ever confirmed: true
See Also: → https://github.com/w3c/csswg-drafts/issues/9131, 2021155
Summary: revert-layer only works if the value is hardcoded → revert-layer on a custom property as a result of a substitution is not properly dealt with
Severity: -- → S3
Priority: -- → P3
Duplicate of this bug: 2037738
You need to log in before you can comment on or make changes to this bug.