web-platform-tests / web-platform-tests/interop
[css-color] handling of powerless and missing components
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 524
- Forks
- 35
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 10
Description
Description
Browsers do not handle powerless and missing components correctly in interpolation or relative color syntax.
This covers both color-mix, relative color syntax and gradients.
This is important to fix as soon as possible because there is no way to detect support for the correct implementation through @supports.
Specification
https://drafts.csswg.org/css-color-4/, https://drafts.csswg.org/css-color-5/
web-feature
color-mix
color-mix-variadic
gradient-interpolation
relative-color
Test Links
https://wpt.fyi/results/css/css-color/parsing/color-computed-none.html?label=master&max-count=1
https://wpt.fyi/results/css/css-color/parsing/color-computed-powerless.html?label=master&max-count=1
Some tests are also present in, but the core aspects around none and powerless components are tested in the files linked above
https://wpt.fyi/results/css/css-color/parsing/color-computed-relative-color.html?label=master&max-count=1
https://wpt.fyi/results/css/css-color/parsing/color-computed-color-mix-function.html?label=master&max-count=1
Additional Signals
No response
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the CSS Color 4 and 5 specifications and the linked WPT files: color-computed-none.html, color-computed-powerless.html, color-computed-relative-color.html, and color-computed-color-mix-function.html. Run the relevant CSS Color tests and compare their coverage of color-mix, relative color syntax, gradients, missing components, and powerless components. Done means the affected behaviors are correctly covered and the tests pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- css
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100