Reject `light-dark()` in `@property` as not computationally independent.
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
| Size Estimate | S |
People
(Reporter: dshin, Assigned: zrhoffman)
References
(Blocks 2 open bugs)
Details
(Keywords: leave-open)
Attachments
(3 files)
As mentioned in bug 1924562 comment 2, light-dark is not computationally independent, which means the declaration should be dropped. But it seems like we just resolve to red.
As observed with the test case in console with CSS warnings/errors enabled, specifying 1em for a <length> property causes the declaration to be dropped, but the first one does not.
| Reporter | ||
Updated•1 year ago
|
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Comment 1•1 year ago
|
||
Bug 1926969 introduces a new example of computational dependence: The
light-dark() function. So specific references to lengths, like
allows_font_relative_lengths, should be generalized.
This patch also renames ParsingMode::DISALLOW_FONT_RELATIVE to
ParsingMode::DISALLOW_COMPUTATIONALLY_DEPENDENT`.
Updated•1 year ago
|
| Assignee | ||
Comment 2•1 year ago
|
||
Because light-dark() dependens on color-scheme, it is not
computationally independent.
| Reporter | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
| Assignee | ||
Updated•1 year ago
|
Comment 4•1 year ago
|
||
Do the devtools show something useful when the declaration is dropped?
| Assignee | ||
Comment 5•1 year ago
|
||
Once bug 1916584 is resolved, DevTools will say:
@property initial-value descriptor ‘light-dark(red, green)’ is not computationally independent.
Comment 6•1 year ago
|
||
| bugherder | ||
Comment 7•5 months ago
|
||
The leave-open keyword is there and there is no activity for 6 months.
:emilio, maybe it's time to close this bug?
For more information, please visit BugBot documentation.
| Assignee | ||
Comment 8•5 months ago
|
||
Before landing the patch, I want to open a spec issue to document this interpretation of the spec.
Updated•5 months ago
|
Comment 9•2 months ago
|
||
Did we file the spec issue here? It seems like we're in a situation where all browsers agree on a specific behaviour, so the longer we wait the higher the chance of getting a compat issue if we try to change anything.
| Assignee | ||
Comment 10•2 months ago
|
||
(In reply to James Graham [:jgraham] from comment #9)
Did we file the spec issue here? It seems like we're in a situation where all browsers agree on a specific behaviour, so the longer we wait the higher the chance of getting a compat issue if we try to change anything.
Sorry for the delay, I have filed the spec issue. https://github.com/w3c/csswg-drafts/issues/12735
Updated•9 days ago
|
Description
•