1827164 - :has() leaves hover highlighting active

Status: RESOLVED DUPLICATE of bug 1792501

(Core :: CSS Parsing and Computation, defect)

Description

[Albert Scheiner [:alberts]]

Attachment: image.png

Originally reported by nemo in https://bugzilla.mozilla.org/show_bug.cgi?id=418039#c69

Testcase demoing an issue where Firefox Nightly 2023-03-24 with :has() enabled leaves hover highlighting active (move down the rows in column E or F), or does not apply hover highlighting (move up from the bottom into the Y cells).
https://m8y.org/tmp/testcase500.xhtml

The mouse pointer is hovering the second row "stuff and more stuff". The first row in the screenshot should not be highlighted anymore.

Comment 1

[David Shin[:dshin]]

Currently expected - invalidation doesn't work properly.

Comment 2

[nemo]

Thank you for filling this bug for me, I wasn't sure if it was new info or not.

Question to dshin - there were 2 buggy behaviours. One was not cleaning up (that seems like it could be described as invalidation) the other part was not highlighting when moving up from the bottom so that the content in "Y" cells should cause highlighting of the previous DOM row.

Does that 2nd part also qualify as "invalidation" 'cause it doesn't seem to involve any cleanup, it just doesn't highlight.

Comment 3

[David Shin[:dshin]]

Invalidation in this context is "current styling is no longer valid" - we never think the background color should change to yellow.

Comment 4

[nemo]

Ok. Gotcha... I mean clearly it semi-works in case where the hover is on the element with the :has. In that case it does highlight, it just doesn't clean up.

Seems mildly different from case where hover is on an element without the :has and it doesn't check the related rules for that different part of the tree, but if they are all covered by same bug, cool ☺

Hopefully at least these are some interesting examples of something that (given the low impact) is now in a real-world system ☺

Comment 5

[random_n0body]

After finally starting to use :has() since it's now widely supported I'm also suffering from this, would be great if this could be fixed

Comment 6

[Tom S [:evilpie]]

This seems fixed to me now, so can probably marked as a duplicate of bug 1792501.

Comment 7

[David Shin[:dshin]]

Confirmed on Windows 10 + today's Nightly 119 - thanks :evilpie!