New wpt failures in /css/css-properties-values-api/registered-property-computation.html
Categories
(Core :: CSS Parsing and Computation, defect)
Tracking
()
People
(Reporter: wpt-sync, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: [wpt])
Syncing wpt PR 45791 found new untriaged test failures in CI
Tests Affected
New Tests That Don't Pass
- /css/css-properties-values-api/registered-property-computation.html [wpt.fyi]
- <color> values are computed correctly [color(from lime srgb g g g)]:
FAIL
(Chrome:PASS
)
- <color> values are computed correctly [color(from lime srgb g g g)]:
CI Results
Gecko CI (Treeherder)
GitHub PR Head
Notes
These updates will be on mozilla-central once bug 1892345 lands.
Note: this bug is for tracking fixing the issues and is not
owned by the wpt sync bot.
This bug is linked to the relevant tests by an annotation in
https://github.com/web-platform-tests/wpt-metadata. These annotations
can be edited using the wpt interop dashboard
https://jgraham.github.io/wptdash/
If this bug is split into multiple bugs, please also update the
annotations, otherwise we are unable to track which wpt issues are
already triaged. Resolving as duplicate or closing this issue should
be cause the bot to automatically update or remove the annotation.
Updated•11 months ago
|
Updated•11 months ago
|
Comment 1•11 months ago
|
||
Reduced testcase:
data:text/html,<body style="background:teal; color: color(from lime srgb g g g)">What color is this text
In Chromium and WebKit, that produces white text. In Firefox, the syntax isn't recognized, so we use the initial color, i.e. black.
This is using the color(from [...])
syntax from css-color-5, aka relative color syntax, so this is just a version of bug 1701488.
(Note, RE the association with the css-properties-values-api metabug: I don't think there's a functional connection between this particular test-failure and the CSS properties & values API; but it is in that test directory, so I suppose the blocking relationship makes sense.)
Comment 2•10 months ago
|
||
Resolved in bug 1898468.
Updated•4 months ago
|
Description
•