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

Re: [csswg-drafts] [selectors] Let :is() have better error-recovery behavior than normal Selectors (#3264)

From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
Date: Mon, 14 Sep 2020 16:51:49 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-692181474-1600102308-sysbot+gh@w3.org>
Just verifying as I write the spec - in <https://github.com/w3c/csswg-drafts/issues/3264#issuecomment-441148706> @ewilligers suggested that we handle "single selector, which is invalid" differently from the rest of the cases, since that has legacy implications, but it looks like we're no longer doing that?

That is, `:is(:unknown)` is valid but matches nothing, just like `:is()` and `:is(:unknown1, :unknown2)`?

-- 
GitHub Notification of comment by tabatkins
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3264#issuecomment-692181474 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 14 September 2020 16:51:51 UTC

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