- From: stiiin via GitHub <sysbot+gh@w3.org>
- Date: Sun, 12 Jan 2025 14:40:40 +0000
- To: public-css-archive@w3.org
I'm not sure what would be the most appropriate place to raise this, but I'm starting to think that the spec phrase > Nor are any of those values used inside `<color-mix()>` or in relative color syntax. is not entirely true in implementations. I wrote [a little test](https://github.com/user-attachments/files/18389724/absolute-color-test.html.txt) (GitHub doesn't let me upload *.html, so *.txt will have to do) and see that both [Firefox (128.6.0esr)](https://github.com/user-attachments/assets/22b42256-b9f9-477b-b7ca-a1aab45341b2) and Chromium (131.0.6778.264) show the same results: * `<device-cmyk()>` can't be used inside `color-mix()`, in line with the spec. * `<system-color>` and `<light-dark()>` can be used inside `color-mix()`, even though the spec seems to prohibit this behaviour. * `<contrast-color()>` can't be used inside `color-mix()`, and is marked as "invalid property value". This is in line with the spec, but also odd, given the behaviour of the implementations with the other types of color values. (This was the reason why I started looking into this.) * `currentColor` can be used inside `color-mix()`. And although I haven't shown it in my test, it's even treated as valid when it's used for the `color` property! Is this a point where the implementations and specification are drifting apart, or are they behaving as specified (and am I misunderstanding the spec)? -- GitHub Notification of comment by stiiin Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9555#issuecomment-2585761035 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Sunday, 12 January 2025 14:40:41 UTC