- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 11 May 2021 00:46:08 +0000
- To: public-houdini-archive@w3.org
The OP's "impedance mismatch" wasn't a big deal, it was just a design question. (And I solved it, by just saying that the Typed OM always represents values as 0-1 or %s; CSS's 0-255 range on RGB is just a weird CSS text-syntax thing.) Notably, this ends up being the same solution that a native JS Color class would do, like in Lea/Chris's library. My experiences so far don't suggest that we'll have much, if any, use-case mismatch. When we do, we can design around it, perhaps with an independent class doing something more directly when the CSS version is too weird/restricted. But for colors? The CSS version appears to be just fine. (The DOMMatrix stuff is an example where the CSS version is indeed too weird/restricted; CSS only uses 3x2 or 4x4 matrixes, but the general use-case wants arbitrary sizes *and* dimensions. It makes sense that handling the arbitrary case in a CSS-specialized class is probably overkill. I'll note, tho, that *we haven't produced an arbitrary Matrix class* for the web, even tho DOMMatrix has been around for years. Hooking things together even when there *is* a slight mismatch at least ensures there's progress on both cases, rather than us only solving the one and leaving the other to languish.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1014#issuecomment-837565886 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 11 May 2021 00:46:09 UTC