Regression involving revert-layer, linear-gradient, custom properties
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr140 | --- | unaffected |
| firefox152 | --- | unaffected |
| firefox153 | --- | unaffected |
| firefox154 | + | affected |
People
(Reporter: kloretz+mozilla, Assigned: emilio)
References
(Regression)
Details
(Keywords: nightly-community, regression)
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:153.0) Gecko/20100101 Firefox/153.0
Steps to reproduce:
https://codepen.io/kirk-l/pen/PwWWVba?editors=1100
This unusual combination of styles is from me using revert-layer to style certain elements on a page with Tailwind CSS, and keep rest of the page's legacy styles from affecting this element.
Strangely, if I change the code any of these ways, the bug doesn't manifest:
- Don't use
all: revert-layer. - Inline the value of
var(--tw-gradient-stops)instead of using a var. - Use the fallback of
var(--tw-gradient-via-stops)directly. (Note this var doesn't exist.) - Inline the value of
var(--tw-gradient-from)instead of using a var. - Don't register the
@property --tw-gradient-from.
The code works as expected on Chrome 149 and Safari 26.5.
Actual results:
One box shows a linear-gradient background, but the box with the style all: revert-layer; does not show the background. This happens in Firefox 153 and Nightly (154)
Expected results:
Two identical boxes should appear. This works on Firefox 152.
Comment 1•8 days ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::CSS Parsing and Computation' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Comment 2•8 days ago
|
||
Rgression window:
https://hg-edge.mozilla.org/integration/autoland/pushloghtml?fromchange=f630dba53a17b5cb588464347209121b4c5040fb&tochange=a0268b86ab8fd3a85ef1adeb2203c64cb341b326
Comment 3•8 days ago
|
||
:emilio, since you are the author of the regressor, bug 2046992, could you take a look? Also, could you set the severity field?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 4•8 days ago
|
||
Thanks. So the issue seems to be that we fail to detect the dependency on the registered color via the property fallback.
| Assignee | ||
Comment 5•8 days ago
|
||
Swarup is currently working on bug 2042898 which should fix this, but I'll try to land something more surgical to fix the regression.
Comment 6•7 days ago
|
||
Set release status flags based on info from the regressing bug 2046992
Comment 7•4 days ago
|
||
Regressor backed out of beta
| Assignee | ||
Comment 8•4 days ago
|
||
[Tracking Requested - why for this release]:
My patch in bug 2021155 will fix this and adds a test, but we should make sure we don't ship this if that doesn't make it on time.
Updated•3 days ago
|
Description
•