- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Dec 2020 13:03:41 +0000
- To: public-houdini-archive@w3.org
> I'm now fairly well convinced that bare numbers passed into the constructor of a CSSRGB object (regardless of how they're passed) should be interpreted the same as bare numbers passed into CSS rgb(). This is an object model of the CSS rgb() function, it needs to match the semantics of the rgb() function. > I'd love to see a generic color object model. And if we create one I'm happy for that to use floats and do away with the 0-255 legacy there. But that's not the scope of this issue or module and we shouldn't let this scope-creep into one. Wait, is that **all** it is doing? An object model of the sRGB-only `rgb()` function? I don't understand how that is useful. Does the `#rrggbb` form have a different object? Does `lab()` have a different object? From [the June 2020 Houdini minutes](https://lists.w3.org/Archives/Public/public-houdini/2020Aug/0002.html) it seemed that there was consensus to have **a color object**, regardless of how it had originally been specified - so that there can be color conversion, color manipulation, and extras like WCAG contrast ratio, gamut mapping, and so forth. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1014#issuecomment-745273990 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 15 December 2020 13:03:42 UTC