- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 26 Oct 2021 00:07:28 +0000
- To: public-css-archive@w3.org
I'm not sure I understand what you're finding confusing/inconsistent. If anything, having L use percentages to refer to the range of the component in both cases seems vastly *more* consistent than forcing authors to remember that L in one case is 0-1 and in another, seemingly identical, case is 0-100 (and in a third case is a 0%-100% range) Note that %s referring to a 0-1 range is *not* consistent thruout the color syntaxes. In rgb(), for example, it covers a 0-255 range. %s are just doing what they're supposed to do - express fractions of a contextually-relevant maximum value (or suitable "unit" value) - same as everywhere else in CSS (and outside of CSS) that uses %s. I'd be strongly against losing the ability to use %s for such an obvious "0 to max" range case. I wish we could use them in the a/b/chroma channels too! -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6761#issuecomment-951433846 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 26 October 2021 00:07:30 UTC