Bug 232368 - [hovering] Should start enriching on mouseDown and forward event to rich hover
Summary: [hovering] Should start enriching on mouseDown and forward event to rich hover
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Text (show other bugs)
Version: 3.4   Edit
Hardware: PC Windows XP
: P4 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Text-Inbox CLA
QA Contact:
URL:
Whiteboard: fix candidate
Keywords:
Depends on:
Blocks:
 
Reported: 2008-05-15 14:03 EDT by Markus Keller CLA
Modified: 2019-09-06 16:15 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 Markus Keller CLA 2008-05-15 14:03:25 EDT 
We should start enriching hovers on mouseDown and forward the mouseDown event to the enriched hover. This would allow the user to start selecting text in a simple hover. Currently, the selection in the simple hover is lost, because enriching only starts on mouseUp, and the rich hover then comes up without a selection.
Comment 1 Markus Keller CLA 2010-07-12 08:39:19 EDT 
I quickly looked into this, and it turned out to be quite complicated.

The problem is that we would have to make sure that *all* events are properly forwarded to the enriched hover. The initial mouseDown is easy, but the following mouseMoves and even more importantly, the mouseUp can occur either in the original browser, in the new browser, or even in another control. In all 3 cases, the enriched browser should see the same events, such that it can e.g. properly select a range of text, and such that a very quick mouseDown/Up on a link really activates the link in the enriched browser.
Comment 2 Eclipse Webmaster CLA 2019-09-06 16:15:38 EDT 
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.