-
Notifications
You must be signed in to change notification settings - Fork 636
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[css-color-5] Only hsl
and hwb
have channel values as percentages in RCS
#9016
Comments
No, it looks like just a failure on my part to update all affected parts of the spec. This edit changed
to
but only for relative You are right that
@tabatkins had pointed out that channel keywords were still using percentage for HWB, and I stated that this was correct because that predated the resolution (which was made on the call that same day). And the spec was even changed elsewhere to refer to these being number for HSL and HWB, see this edit, as part of #8322. So I should fix that, for consistency. Thanks for your careful review! |
Also from the intro to RCS;
|
Relevant tests to check: Add subtests with calc(), to check correct types used, on:
|
One more :) csswg-drafts/css-color-5/Overview.bs Line 1417 in 70622d0
|
Thanks! |
Thank you for these edits and clarifications 🙇 |
(Leaving the issue open so I don't forget about the need for testcase review and supplementation) |
I've added a few tests that should also cover this issue : web-platform-tests/wpt#43931 |
Cheers, I just approved them. |
The spec is now correct and the tests are updated, so I believe this can be closed. |
I was going over the list of changes in
css-color-5
and I noticed that onlyhsl
andhwb
have channel keywords in RCS that have percentage values.Both however also allow number values as regular arguments.
In
css-color-5
these are both valid and equal :hwb(90deg 25% 25%)
hwb(90deg 25 25)
@svgeesus is there a reason not to give the channel keywords the number type?
That would make these two color functions more consistent with every other color function.
The text was updated successfully, but these errors were encountered: