192065 - hover with nested elements breaks links

Status: RESOLVED DUPLICATE of bug 183502

(Core :: DOM: UI Events & Focus Handling, defect)

Description

[Shahms E. King]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030127
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3b) Gecko/20030127

I have a reduced test case that demonstrates a number of combinations, some of
which work, some don't.  However, the biggest example is the pure css menus
example at css/edge.  These used to work, but no longer do (Linux, 1.3b-gtk2 CVS
and 1.2.1).  When you attempt to click on the link, the :hover no longer
applies, causing the clicked link to disappear and not be followed.

Reproducible: Always

Steps to Reproduce:
Create a list with anchors and nested elements.
create an li:hover rule to show the nested elements on mouse over
attempt to click the link
Actual Results:  
Nested elements disappear and link is not followed.

Expected Results:  
Link should be follow, irrespective of what happens to the elements

Comment 1

[Shahms E. King]

Attachment: simplified test-case for nested :hover

Simplified test case demonstrating 4 different effects from the same 2 css
rules, depending entirely on how the child elements are nested.

Comment 2

[Boris Zbarsky [:bzbarsky]]

All those tests work for me, linux trunk build 2003-02-04-08....

Comment 3

[Andrew Schultz]

this appears to be mostly a dupe of bug 102578 - clicking wrongfully fires
onmouseout 

to verify (see bug 102578 comment 31):
switch to sloppy mouse focus without click-to-raise
==> testcase works
switch to click-to-focus or click-to-raise
==> testcase fails

mouseout means the hover is cancelled and the link disappears before the click
handler fires (explains testcases 1 & 3).  I don't know why the second link is
unresponsive...

Comment 4

[alanjstr]

The menus on http://devedge.netscape.com are also broken because of this.  

Comment 5

[Boris Zbarsky [:bzbarsky]]

No, they're not.  They're broken because of a totally different, much more
recent, problem.  See bug 196603.

Comment 6

[José Jeria]

dupe of bug 183502?

Comment 7

[alanjstr]

Yep, it's a dupe.  Though they should both probably be duped against bug 102578

Comment 8

[Boris Zbarsky [:bzbarsky]]

I'd leave them both open and retest when bug 102578 is fixed.... It's hard to
tell whether they are really dups as things stand.

Comment 9

[alanjstr]

At a minimum I'd say this one is a dupe of bug 183502

Comment 10

[Boris Zbarsky [:bzbarsky]]

Ah, true.  That's the same url...

*** This bug has been marked as a duplicate of 183502 ***