Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 345915 - Browser content is selectable in IE under some constellation
Summary: Browser content is selectable in IE under some constellation
Status: ASSIGNED
Alias: None
Product: RAP
Classification: RT
Component: RWT (show other bugs)
Version: unspecified   Edit
Hardware: PC Windows 7
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Project Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-16 06:56 EDT by Ivan Furnadjiev CLA
Modified: 2011-05-16 10:07 EDT (History)
1 user (show)

See Also:


Attachments
Screenshot (52.15 KB, image/png)
2011-05-16 06:56 EDT, Ivan Furnadjiev CLA
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ivan Furnadjiev CLA 2011-05-16 06:56:27 EDT
Reproducible with Controls Demo -> SashForm tab under IE. Start slowly moving (dragging) the sash to the left. At some position, the browser content is partly or fully selected. If not reproducible from the first time...play with the sash (left/right) a little bit.
Comment 1 Ivan Furnadjiev CLA 2011-05-16 06:56:57 EDT
Created attachment 195716 [details]
Screenshot
Comment 2 Tim Buschtoens CLA 2011-05-16 10:07:41 EDT
Okay, so the problem is that the TextArea in that scenario has its "selectable" (qooxdoo) property set to true, and the selection starts WITH the element, but not IN the element. Its actually easily reproduceable with many textfields in RAP: Just press down on near its border and move the mouse. 

The mechanism preventing unwanted selection in IE is in EventHandler#_onselectevent. It checks for the widgets (in this case Text) "selectable" property, and cancels the event if its not set to true. Since the source of the event is apparently not where the mouse is pressed down, but the first selected element, one solution might be to prevent mousedown-events like done in FF in Application.js_onFFMouseDown. Another way might be to probe the selection range object and check for it to not include any html-elements (perhaps text and htmlText should be matching.) In any case these changes have to be done and tested carefully, as selection can be handled very differently between all browsers and widgets.