- From: Kevin Babbitt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 09 Aug 2024 20:17:31 +0000
- To: public-css-archive@w3.org
Agenda+ to clarify the intent of the WG in the resolution taken previously. The question originally posed was, by my read, a narrow matter of: *when* a relative color is serialized as `rgb()`/`rgba()` or `hsl()`/`hsla()`, whether the form without the `a` should be used. Currently, [per spec](https://drafts.csswg.org/css-color-5/#serial-relative-color), the above only happens when a relative color is based on `currentcolor`. For relative colors that are resolvable at parse time, they serialize as their resolved form. And per the same spec section, the resolved form serializes as `color(srgb ...)` since the mixing color space was srgb or hsl. Blink and Gecko have both shipped this behavior. Some [WPT changes](https://github.com/web-platform-tests/wpt/commit/072e7fd7d7391bb49370e6100610e529d6c9d2b5#diff-3c11dc425e69e4b485a6e9a265d604152cfaa9ba6578de7777a73443badfa682) landed recently that appear to interpret the resolution more broadly: that relative colors declared in `rgb()`/`rgba()`/`hsl()`/`hsla()` *should* serialize in their declared forms rather than their resolved forms. In fact, the WPT changes go one step further and assert that relative colors declared with other functions such as `lab()` or `lch()` should also serialize in their declared forms rather than resolved forms. (See color-valid-relative-color.html in the linked commit.) Unfortunately, I did not realize that 'should' implication at the time we took the resolution, nor did I realize that it would constitute a break from shipped behavior. :| The question of whether to serialize in declared or resolved form is asked more directly in #10305, which the WG has not resolved on. Because that would be a breaking change, it's not clear to me we can make it absent compat analysis. I'm happy to do that analysis; however these changes also impact Interop2024, and the remaining runway for that is short. I can't promise I'd be able to get good enough data for the WG to resolve and implementations to adopt the change by the end of the year. How does the rest of the WG understand the question and resolution here vs 10305? cc @emilio -- GitHub Notification of comment by kbabbitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10327#issuecomment-2278680761 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 9 August 2024 20:17:32 UTC