- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Fri, 02 Sep 2022 12:54:58 +0000
- To: public-css-archive@w3.org
> The way the jQuery selector engine works (and have worked for a long time), the selector is tried against querySelectorAll with minor modifications and if it fails, it goes through the internal selector engine. It's either-or. Shouldn't jQuery check `CSS.supports("selector(:has(....))")`, which should be unforgiving per spec? See https://github.com/w3c/csswg-drafts/issues/7280 -- GitHub Notification of comment by emilio Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1235472172 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 2 September 2022 12:55:00 UTC