Bug 331537 - [client] mouseup outside document is lost
Summary: [client] mouseup outside document is lost
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 1.4   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-12-01 08:33 EST by Tim Buschtoens CLA
Modified: 2011-02-01 10:35 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2010-12-01 08:33:15 EST
In Firefox and Webkit a releasing the mouse-button outside of the document is not recognized. Therefore all drag&drop-like operations and the abandon-behavior of buttons does not work correctly afterwards. This should be fixed by faking a mouseup on reentry into the document.
Comment 1 Tim Buschtoens CLA 2011-02-01 10:35:42 EST
Seems this wont be possible: There is no way to detect on a mouseMove event if a button is pressed or not. The only browser where this is possible is IE, which alrady does it in our current implementation. 

It should be possible to detect the mouse leaving the document and fire a mouseup then, but this would only shift the problem from potentially missed mouse-events to potentially wrongfully added mouse events. It would mean that any DND-operations will be aborted if the mouse leaves the browser, which is a no go in my opinion.

This issue is most promimently visible with the new non-native scrollbars:
Scrolling from one end of an area to another is often done by dragging the thumb all the way to its limit in anexaggerated movement, leaving the browser-window.
perhaps we could implement a scrollbar-specific solution: Release the scrollbar on its current position if the mouse leaves the browser, but fake no mouseup for any of the other widgets.