W3C home > Mailing lists > Public > public-css-archive@w3.org > May 2020

Re: [csswg-drafts] [css-values]: Express conditional values in a more terse way (#5009)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Thu, 28 May 2020 00:04:26 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-635008765-1590624265-sysbot+gh@w3.org>
> I think that in most cases, authors would keep both, the numeric index (or possibly textual key) and the set of values, in variables.

I don't see why this would be the case.

The point of nth-value() is that it lets authors keep the values right at the point of application, and do a minimal amount of work in MQs to set up the index variable.

If you're going to set up all your values as variables *anyway*, you might as well go put them in your MQ and skip usage of nth-value entirely, right? No reason to introduce the additional indirection.

(Authors can still reasonably use variables in their values anyway, of course, but I don't think it's reasonable to assume they'll use them for *all* their values.)

GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5009#issuecomment-635008765 using your GitHub account
Received on Thursday, 28 May 2020 00:04:27 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:42:07 UTC