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:
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...
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:
I think Blink's behavior (which if I understand correctly is "only apply the quirk if the only thing in the selector is
:hoveror:activeand 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...