291507 - Sometimes hovering over drop down also hovers underlying link

Status: RESOLVED FIXED

(Core :: Web Painting, defect)

Description

[Martijn Wargers (dead)]

Follow the steps in the upcoming testcase.
Sometimes when hovering over the drop down, the cursor changes in a hand and the
underlying link gets a green background color. This should not happen.

Doesn't happen with 2005-03-06 build, happens with 2005-03-07 build.
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2005-03-06+05%3A00%3A00&maxdate=2005-03-07+09%3A00%3A00&cvsroot=%2Fcvsroot

In fact in the 2005-03-06 build, the cursor always stays default and links don't
ever react/change color when the drop down is open (which is also what IE6 does,
only IE6 does that also for the chrome area, Mozilla not). This is in fact
different from the behavior from Mozilla1.7 where links change color when
hovered over while the drop down is opened.

Comment 1

[Martijn Wargers (dead)]

Attachment: Testcase

The position:fixed containing div is necessary to trigger the bug.

Comment 2

[Martijn Wargers (dead)]

Attachment: Screenshot of the bug

This is what I meant. A picture is sometimes easier to explain a bug.

Comment 3

[Martijn Wargers (dead)]

Forgot to say, it happens intermittently. I get a 'flickering' behavior when
hovering over the drop down.

Comment 4

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Could be a duplicate of bug 290673 or 291222. I can't reproduce it myself, which
suggests bug 290673.

Comment 5

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Can someone confirm whether this is fixed or not?

Comment 6

[Martijn Wargers (dead)]

No, not fixed, I can still see the bug with a 2005-05-06 trunk build.

Comment 7

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Probably bug 276892.

Comment 8

[Robert O'Callahan (:roc) (email my personal email if necessary)]

Martijn, could you confirm that by backout? I still don't see how that could
cause this.

Also, can you tell me whether this happens when you click, release, and then
hover, or when you click, hold and hover, or both?

Thanks!

Comment 9

[Martijn Wargers (dead)]

No, backing out the patch of bug 276892 doesn't fix this bug (unless rebuilding
/layout is not enough?).
Like I said in comment 0, before 2005-03-07 builds the cursor is 'locked' when
the drop down is open, so the issue could already be there in those builds, but
not exposed.

Comment 10

[Martijn Wargers (dead)]

Attachment: Sort of a fix (at least to me)

This fixes the bug for me, in the sense that mouseenter (hover) events get
consumed in the content area for comboboxes. This is also what IE is doing so
in
windows at least, it is correct behavior. In fact, this reverses the
behavior like it was.

In general, mouseenter (hover) events seem to get consumed with all popup types
(except autocomplete) in Windows. That's not what Mozilla is doing currently
for windows.

Comment 11

[Robert O'Callahan (:roc) (email my personal email if necessary)]

I seem to recall a long bug somewhere discussing the issues around having popups
capture all mouse events on Windows. Ere, do you recall the bug, or have any
insight into this problem here?

Comment 12

[Ere Maijala (slow)]

I'm not sure, but bug 20022 and bug 284664 might be related.

Comment 13

[Ere Maijala (slow)]

Hmm... this might also be related to MouseTrailer sending an exit to the
underlying element (see bug 297561).

Comment 14

[Martijn Wargers (dead)]

Ok, this seems fixed now that the fix for bug 297561.
One nit though: the border area doesn't stop the hovering over the underlying link.
And for windows, the behavior mentioned in comment 10 is desirable.

Comment 15

[Martijn Wargers (dead)]

Ok, the issue mentioned in comment 10 is bug 123582 (although it was fixed
during a period after that bug is filed).
This bug is fixed by bug 297561.

Comment 16

[Martijn Wargers (dead)]

Er, I meant the issue in comment 10 is bug 14953.