244708 2022-09-02 02:22:35 -0700 :has() selector does not accept forgiving selector list 2023-10-21 14:28:06 -0700 1 1 1 Unclassified WebKit CSS Safari Technology Preview Unspecified Unspecified RESOLVED INVALID https://bugs.webkit.org/show_bug.cgi?id=249914 BrowserCompat, InRadar P2 Normal --- 1 rune.lillesveen webkit-unassigned bramus karlcow koivisto m.goleb+bugzilla ntim webkit-bug-importer oldest_to_newest 1895734 0 rune.lillesveen 2022-09-02 02:22:35 -0700 The :has() selector takes a <forgiving-relative-selector-list>[1], but a rule like :has(:unknown) {} is fully dropped in WebKit. There is a failing wpt test in [2]. [1] https://drafts.csswg.org/selectors/#typedef-forgiving-relative-selector-list [2] https://wpt.fyi/results/css/selectors/has-error-recovery.html?label=experimental&label=master&aligned 1895746 1 m.goleb+bugzilla 2022-09-02 03:48:57 -0700 Note that implementing `:has` according to the spec breaks `:has` usage with jQuery for almost all versions in use in the wild: https://github.com/jquery/jquery/issues/5098 1895765 2 koivisto 2022-09-02 05:26:15 -0700 We currently do use forgiving parsing for :has() but still fail the selector if the selector lists ends up empty. That is :has(:foo, bar) { } is valid and parses to :has(bar) { } but :has(:foo) is invalid. 1895766 3 koivisto 2022-09-02 05:26:34 -0700 I suppose this saves us from the jQuery problem. 1895798 4 m.goleb+bugzilla 2022-09-02 10:02:28 -0700 See https://github.com/w3c/csswg-drafts/issues/7676#issuecomment-1235724730 The WebKit behavior still breaks some jQuery selectors. True, it doesn't break: ``` div:has(span:contains('Item')) ``` but it still breaks: ``` div:has(div, span:contains('Item')) ``` Maybe that latter kind of selectors is not used as often in the wild. 1896325 5 m.goleb+bugzilla 2022-09-05 05:51:59 -0700 A full fix for future jQuery versions requires implementing bug 244808 so please have a look at this. 1897196 6 webkit-bug-importer 2022-09-09 02:23:16 -0700 <rdar://problem/99736653> 1898725 7 karlcow 2022-09-15 09:35:06 -0700 Note that there are discussions about this behavior being beneficial currently, as it doesn't break jQuery. See the discussion in https://github.com/w3c/csswg-drafts/issues/7676 1898727 8 karlcow 2022-09-15 09:36:50 -0700 oops hit return too early. Chrome 106 copies the behavior of Safari. 1986705 9 ntim 2023-10-21 14:28:06 -0700 No longer valid with bug 249914.