Simplifying the hover and active quirks? #75
Description
What is the issue with the Quirks Mode Standard?
https://quirks.spec.whatwg.org/#the-active-and-hover-quirk has a list of conditions that doesn't keep up with new CSS features.
It seems implementations do subtly different things that end up in subtle bugs like https://bugzilla.mozilla.org/show_bug.cgi?id=1856285:
- Gecko: https://searchfox.org/mozilla-central/rev/47a0a01e1f7ad0451c6ba6c790d5c6855df512c1/servo/components/selectors/matching.rs#624
- Blink: https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/core/css/selector_checker.cc;l=185;drc=e7a3efac5cc6bb943f7943fe3ef0569b8aa77d7d
- WebKit: https://searchfox.org/wubkat/rev/fe11bcadadbf8b7ad5f95d337b6842b4b42982ec/Source/WebCore/css/SelectorChecker.cpp#624
I think Blink's behavior (which if I understand correctly is "only apply the quirk if the only thing in the selector is :hover or :active and it's not nested) is simpler, and I think we should change the spec to match that, if my understanding is correct.
@lilles / @andruud: Could you confirm my read of Blink's source is correct?
@annevk: Would WebKit be fine with that change? If so I'd be happy to send a PR.
cc @whatwg/css, I assume making stuff less quirky is generally good if we can get away with it...