38442 - Scrolling a SELECT widget causes mouse events to bleed through to the page behind it

Status: VERIFIED DUPLICATE of bug 38393

(Core :: Layout: Form Controls, defect, P3)

Description

[Leonid]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; m16) Gecko/20000505
BuildID:    2000050513

When scrolling the SELECT widget using either the thumb or the arrows, it causes
mouse events to bleed through to the page behind it, resulting in selected text
or clicks sent to other widgets on the form.


Reproducible: Always
Steps to Reproduce:
1.  Drop down the Component list on the bugform
2.  Scroll the Component list
3.  Note the text selected when the mouse is moved
4.  Click where the drop down arrow of the Platform widget would be if the list
weren't in the way
5.  Notice that the Platform widget drops down


Actual Results:  Same as noted in the list above

Expected Results:  Mouse events should not be going to the page itself, but
handled by the widget and discarded.

Comment 1

[John Morrison]

-> HTML Form Controls   ... another artefact is that you can do a drag select
of the page contents while the drop-down list is up on screen, resulting in 
the attached image.

Comment 2

[John Morrison]

Attachment: HTML Select popup moved to the end of page, away from it's parent control location

Comment 3

[John Morrison]

The behaviour noted in this bug report is windows only.

Linux works correctly. 

Mac, though, is not working correctly at all -- the native scrollbar cannot be 
dragged, does not respond to onclick on the arrow icons, and does not scroll 
with keyboard commands when the mouse is over the list (mozilla 2000050510). 
Is this a known problem for Mac?

Comment 4

[Hugh Kennedy]

the behavior seen by John Morrison is  a dup of bug 27661, although the rest of
this appears to be something different.

Comment 5

[Leonid]

The behavior I reported was using the grafx scroll bars, but I have since
verified it for the standard Windows scroll bars as well.

Comment 6

[rods (gone)]

may be a dup of 38393

Comment 7

[Blake Ross]

*** Bug 39235 has been marked as a duplicate of this bug. ***

Comment 8

[rods (gone)]

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

Comment 9

[Stephen Walker]

verifying