- From: Anne van Kesteren via GitHub <sysbot+gh@w3.org>
- Date: Mon, 07 Oct 2024 09:09:53 +0000
- To: public-css-archive@w3.org
annevk has just created a new issue for https://github.com/w3c/csswg-drafts: == CSS color serialization and <input type=color> with alpha/colorspace == For https://github.com/whatwg/html/pull/10456 we allow `<input type=color>`'s internal color to be set as follows: * An arbitrary value that parses as a CSS color (`value` attribute). * An end user selected CSS color through some UI. This color is then color space converted depending on the `colorspace` attribute and serialized for API purposes and form submission. We only support the 'srgb' and 'display-p3' color spaces for now. When `colorspace` is set to "`limited-srgb`" (default value) and the `alpha` attribute is not set we specifically instruct CSS color serialization to use the hexadecimal syntax for compatibility. Otherwise we follow CSS color serialization directly. However, what is not clear currently is what kind of normalization color space conversion applies. E.g., if the input is `lab(51.2345% -13.6271 16.2401)`, is the output going to be `color(srgb 0.41587 0.503670 0.36664)`? How is that defined? What if the input is `#11223344`? Ideally from a web developer perspective I think it would always use `color(srgb ...)` or `color(display-p3 ...)` unless we needed compatibility with the existing input as described above. But now I'm wondering if that is actually what we ended up requiring or if there are some other loose ends to tighten up. cc @svgeesus @lukewarlow @weinig Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11008 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 7 October 2024 09:09:54 UTC