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

Just verifying as I write the spec - in <> @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 using your GitHub account

Sent via github-notify-ml as configured in

Received on Monday, 14 September 2020 16:51:51 UTC