Bug 387033 - [Scripting] Refactor Mouse event handling to better support ClientScripting
Summary: [Scripting] Refactor Mouse event handling to better support ClientScripting
Status: NEW
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: 2.0   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-08-10 12:18 EDT by Tim Buschtoens CLA
Modified: 2013-08-22 08:58 EDT (History)
1 user (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Buschtoens CLA 2012-08-10 12:18:39 EDT 
The client-side mouse events currently make no distinction between no button pressed and left button pressed. (The only exception is IE7+8, which isn't W3C-conform). This is not relevant for mouse up/down/click event, but very much for move/enter/exit. While we don't support those on the server, they are supported in ClientScripting, where it might be needed for DND-like features. 

There seems to be no bulletproof way to detect this (as the button could be released outside the document), but it should work at least as long as the mouse stays in the document.