| Summary: | Browser content is selectable in IE under some constellation | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [RT] RAP | Reporter: | Ivan Furnadjiev <ivan> | ||||
| Component: | RWT | Assignee: | Project Inbox <rap-inbox> | ||||
| Status: | ASSIGNED --- | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P3 | CC: | tbuschto | ||||
| Version: | unspecified | ||||||
| Target Milestone: | --- | ||||||
| Hardware: | PC | ||||||
| OS: | Windows 7 | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
|
Description
Ivan Furnadjiev
Created attachment 195716 [details]
Screenshot
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. |