- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Wed, 30 Nov 2022 16:28:42 +0000
- To: public-css-archive@w3.org
Okay, so I gave [three options earlier](https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1235773031), but in the Sep 16 meeting @fantasai gave a fourth option (maybe an option 2b from my list?) where we keep forgiving-selector-list, but *only* use it in :is() and :where(). Everywhere else we stick to the existing non-forgiving behavior. * This fixes the question at hand - jQuery will go back to working correctly when an author uses a jquery-specific selector inside of (what they assumes was) jquery-specific :has() * This makes :has() (and all similar selector arguments, like `:nth-child(of)`) consistent with :not(), which is non-forgiving. * Forgivingness becomes a special property of :is()/:where(), which seems more learnable than a more arbitrary set of selectors influenced by history. So I propose we take on fantasai's suggestion. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1332429146 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 30 November 2022 16:28:44 UTC