All users were logged out of Bugzilla on October 13th, 2018

[STATE] Drag element outside the screen and release mouse button don't causes the event.

NEW
Unassigned

Status

()

P3
normal
19 years ago
9 years ago

People

(Reporter: mgalli, Unassigned)

Tracking

1.8 Branch
Future
x86
Windows 98
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

19 years ago
Build: 2000022908
Win98

Not sure if it's DOM2 or Event Handling:

Reproduce:
. Start dragging the N, move outside the screen area.
. Release the mouse,
. continue moving the mouse inside the screen area.

note:
. See that is the N is still moving. In this source code, the endDrag was not 
called when released the button outside the screen.

Comment 1

19 years ago
Confirmed, Marking as NEW.
Status: UNCONFIRMED → NEW
Ever confirmed: true

Comment 2

19 years ago
*** Bug 24325 has been marked as a duplicate of this bug. ***

Comment 3

19 years ago
Adding [STATE] keyword to bugs dealing with bad internal state created by lost 
or overridden events.
Status: NEW → ASSIGNED
Summary: Drag element outside the screen and release mouse button don't causes the event. → [STATE] Drag element outside the screen and release mouse button don't causes the event.
Tried this on NT, build 2000072508, and could not reproduce this. Can others?
Doh, I can reproduce this. Forget the earlier comment.
This bug has been marked "future" because the original netscape engineer
working on this is over-burdened. If you feel this is an error, that you or
another known resource will be working on this bug,or if it blocks your work in
some way -- please attach your concern to the bug for reconsideration.
Target Milestone: --- → Future

Comment 7

19 years ago
Mass update:  changing qacontact to ckritzer@netscape.com
QA Contact: janc → ckritzer

Comment 8

18 years ago
Updating QA Contact.
QA Contact: ckritzer → lorca
Reassigning QA Contact for all open and unverified bugs previously under Lorca's
care to Gerardo as per phone conversation this morning.
QA Contact: lorca → gerardok

Comment 10

18 years ago
QA contact updated
QA Contact: gerardok → madhur

Updated

17 years ago
QA Contact: madhur → rakeshmishra

Updated

16 years ago
QA Contact: rakeshmishra → trix

Comment 11

16 years ago
For whomever might be listening, in case this bug is still active:

WORKSFORME on XP Pro SP1 using 2003010908

Comment 12

16 years ago
Argh... I did not well understood the instructions to reproduce. Please ignore
my previous comment. There is a bug here. 
It seems that onmouseup is not detected if the mouse is outside the browser
viewport.
Sorry for the previous comment.

Comment 13

15 years ago
.
Assignee: joki → saari
Status: ASSIGNED → NEW
QA Contact: trix → ian

Comment 14

14 years ago
Still a bug on Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5)
Gecko/20041107 Firefox/1.0

other applications always maintain control of the mouse pointer until mouse
button is released; javascript apps cannot maintain awareness of the mouse
status if the mouse leaves the document

Comment 15

12 years ago
When trying the demo at provided URL, I get the expected results: releasing mouse button when outside window viewport does fire mouseup event in Seamonkey 1.5a rv:1.9a4pre build 2007042110 under XP Pro.

Version -> 1.8 Branch

Note that this bug is related to bug 341565 
Version: Trunk → 1.8 Branch

Comment 16

10 years ago
Confirmed on Thunderbird version 2.0.0.17 (20080914)  on OS X 10.5

If you begin selecting text inside the compose window, but release the mouse button outside the compose window, and then move the mouse back into the compose window, the selection is still active and follows your mouse around.

This bug is very annoying because It is common (especially when a text area borders the window edge) to finish a gesture with the cursor outside the application window. 

If the reason involves some JS security limitation about mouse events outside the application and/or it is not possible to pick up the mouse up event, but it is possible to detect the mouse state on entry/exit from the region, then the following algorithm could be used:

If selection is active:

On region exit:
If mouse button is down save exit position.

On region entry:
If mouse button is down, continue selection behavior.
If mouse button is up, change state to button up/send up event, discontinue selection behavior, set selection to saved exit position.
Assignee: saari → nobody
QA Contact: ian → events
You need to log in before you can comment on or make changes to this bug.