- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Dec 2022 17:04:01 +0000
- To: public-css-archive@w3.org
@anttijk The problem isn't someone explicitly writing an empty :is(), it's someone writing a normal selector list into the pseudo-class and all of them turning out invalid. If *that* makes *the entire selector* invalid, but having *one* recognized selector keeps it valid, it's a weird effect, as @romainmenke just pointed out. (Whether an explicitly empty :is() is valid or not is a separate question that I don't particularly care about. We can write the grammar either to allow it or forbid it, but serialization will be trickier if we forbid it, since we drop the invalid selectors from the argument.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1341285155 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 December 2022 17:04:03 UTC