- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 15 Dec 2020 01:38:06 +0000
- To: public-houdini-archive@w3.org
> e.g. does let x = new CSSRGB() throw an exception or is it simply new CSSRGB(0, 0, 0). Similarly, what if an author calls new CSSRGB(42) should that throw or just be new CSSRGB(42, 0, 0)? Both throw. Those are required arguments in CSS, and there's no particularly good reason to change that in the JS representation, I believe. There's not really a meaningful sense in which 0 is a "default" value for any of the color channels. > But that's actually inconsistent with your "passing a raw JS number is equivalent to passing a CSSUnitValue(x, "number")" so will cause even more author confusion IMO. Yes, it is inconsistent, but in a different realm. My current spec text has JS numbers be `<percentage>` for *all* colors; JS numbers are `<number>` elsewhere where numbers are the only sensible thing. I think this is a simple enough boundary that the confusion will be low, enough to be outweighed by the convenience of being able to write, say, `CSS.hsl(CSS.degrees(60), 1, .5)` over `CSS.hsl(CSS.degrees(60), CSS.percent(100), CSS.percent(50))`. > Where can we find this draft? It's not anywhere in this repo. Searching for CSSRGB in the repo yielded no results. There are a lot of design decisions involved that are more substantial than constructor arguments, and it would be good to discuss and iterate earlier rather than later. It's still an in-progress edit right now, I'll have first draft up soon. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/1014#issuecomment-744978406 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 01:38:07 UTC