285524 - Mouse events are not sent when click-dragging in some cases

Status: RESOLVED EXPIRED

(Core :: DOM: Events, defect)

Description

[Christopher Kings-Lynne]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050225 Firefox/1.0.1

If you mouse down on a select list control, then drag away, mouse events are not
sent to any other controls.

Reproducible: Always

Steps to Reproduce:
1. Visit the test url
2. Click and hold on the background somewhere then mouseup on the right select
box, see alert appears
3. Click and hold on the left select box, then mouseup on the right select box,
see no alert appears
4. Try steps 1-3 in Internet Explorer and it works just fine.

Actual Results:  
Mouse up event is not fired at all.

Expected Results:  
The mouseup event on the right select box should have been fired.  In fact,
mouseover, mouseout and mousemove don't seem to be fired either.  This makes
implementing drag and drop really nasty.

Comment 1

[Christopher Kings-Lynne]

Furthermore, if you mousedown on the right select box, drag, and mouseup on the
left, notice the alert appears, even though there is no mouseup event on the
left select box.  In Internet Explorer, no alert appears, so it is probably
firing the onmouseup even for the left select box correctly.

Comment 2

[Boris Zbarsky [:bzbarsky]]

I believe this is the expected behavior when events are captured (which they are
for <select>s)...  Otherwise, for example, drag-scrolling <select>s would not work.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.