attr() and style queries don't work together
Categories
(Core :: CSS Parsing and Computation, defect, P3)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox-esr115 | --- | unaffected |
| firefox-esr140 | --- | unaffected |
| firefox-esr153 | --- | unaffected |
| firefox155 | --- | wontfix |
| firefox156 | --- | wontfix |
| firefox157 | --- | fixed |
People
(Reporter: jakea, Assigned: emilio)
References
(Regression)
Details
(Keywords: regression)
Attachments
(1 external file)
https://random-stuff.jakearchibald.com/bug-repros/attr-in-style-queries/
The first box should be green.
| Assignee | ||
Comment 2•1 month ago
|
||
Yeah mozregression --launch 2026-06-16 behaves as expected.
| Assignee | ||
Comment 3•1 month ago
|
||
That is, in the places where we are deciding to potentially replace a
value with another (the property deduplication, and the fast path to
avoid the cascade).
Otherwise we'd fail /css/css-values/attr-universal-selector.html
Updated•1 month ago
|
Comment 4•1 month ago
|
||
Set release status flags based on info from the regressing bug 2047198
:sukil, since you are the author of the regressor, bug 2047198, could you take a look?
For more information, please visit BugBot documentation.
Updated•1 month ago
|
Comment 7•1 month ago
|
||
| bugherder | ||
| Reporter | ||
Comment 8•1 month ago
|
||
This was spotted externally https://bsky.app/profile/alexlehner86.bsky.social/post/3mv3efru7rk26 so it might be worth an uplift.
But then, with "new attr" being so new, it could probably just ride the new faster trains.
Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/62590 for changes under testing/web-platform/tests
Upstream PR merged by moz-wptsync-bot
Updated•1 month ago
|
Description
•