Closed
Bug 211398
Opened 21 years ago
Closed 20 years ago
strange behaviour of mouse event handler (like MSIE setCapture)
Categories
(Core :: DOM: Events, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: jimson, Assigned: saari)
References
()
Details
User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030519
Build Identifier: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.3.1) Gecko/20030519
Block element with style="position: absolute" receive mouse events even when
pointer is outside the document.
As far as I understand, it is not provided by DOM.
Here is simple example for 'mousedown' event inside
DIV with style="position: absolute;
http://dwarf.mostcom.ru/~jimson/mousemove.html
Handler inside DIV receive 'mousemove' and 'mouseup' events even if
mouse pointer moved outside browser window (!)
Is it a bug or a feature ?
It work in mozilla 1.3.1, 1.2.1, netscape 7.0 (MS Windows, FreeBSD, Linux).
Reproducible: Always
Steps to Reproduce:
1. open http://dwarf.mostcom.ru/~jimson/mousemove.html
2. try to 'pull' (as drag-n-drop) green box outside browser window
3. look at numbers inside green box
Actual Results:
astonishment :)
Expected Results:
Block element should not receive mouse events when pointer leave it.
Comment 1•21 years ago
|
||
if no mousekey is pressed, it is working, numbers are updated as long as the
pointer is inside the box.
If a mousekey is pressed (Mousedown), there are three cases:
1. mousekey pressed outside of box: ok
count starts when pointer enters box and stops when pointer leaves box.
2. mousekey pressed outside of window: ?
count never starts, not when entering or leaving box or window.
3. mousekey pressed inside of box: this bug
count starts when pointer moves, doesn´t stop on leaving box or window,
but stops when key is released.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 2•21 years ago
|
||
This is already filed, if I recall correctly... please find the original bug report.
Whiteboard: DUPEME
Comment 3•20 years ago
|
||
Looks like the patch in bug 53966 fixed this bug, too. Tested with a Linux trunk
build from today.
Status: NEW → RESOLVED
Closed: 20 years ago
Resolution: --- → FIXED
Whiteboard: DUPEME
You need to log in
before you can comment on or make changes to this bug.
Description
•