- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Mon, 10 Jan 2022 18:38:48 +0000
- To: public-css-archive@w3.org
Remind me what the reason is for an author to explicitly convert color spaces? Is it just to get a good default interpolation without having to specify an interpolation strategy (or in places where we're not adding the ability to specify one)? If so, then the 0-arg version makes sense to me. It reads well and the meaning is obvious; it clearly communicates "I'm making no change to this color besides the colorspace inherent in the wrapping function". The non-zero-but-not-full version makes less sense to me. You'd only be able to omit from the end, so the usefulness is entirely dependent on the ordering of a particular function; for example, HSL and LCH are exactly backwards in their arg ordering, so you could achieve some effects in one that you couldn't with the other, for no particular reason other than accidents of naming history. The lack of one or two components is also much less visually obvious than the *complete* lack of components. We do allow alpha to be omitted from the syntax, whereupon it means "take from the origin color", but the presence or absence of alpha is decently signaled by the `/` character. All in all, adding this just to save 2-4 characters (depending on whether you're omitting 1 or 2 components) doesn't seem like it pays for itself, imo. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6938#issuecomment-1009231960 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 10 January 2022 18:38:49 UTC