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

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

From: Eric Willigers via GitHub <sysbot+gh@w3.org>
Date: Tue, 25 Aug 2020 00:52:33 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-679439253-1598316751-sysbot+gh@w3.org>

> should `:is(:nonsense)` serialize just as `:is()`? Should that be special-cased to never match?

> Then, of course `:is()` should be parseable too...

Yes, I was going to serialize `:is(:nonsense)` as `:is()` in dev tools, and treat `:is()` as a valid selector that never matches.

Is serialization of selectors web exposed, i.e. testable in WPTs?

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 25 August 2020 00:52:38 UTC

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