Bug 72812 - [KeyBindings] interactions: Edit box and scroll bar context menus do not have self documented keyboard shortcuts
Summary: [KeyBindings] interactions: Edit box and scroll bar context menus do not have...
Status: ASSIGNED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.0   Edit
Hardware: All All
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard:
Keywords: helpwanted
Depends on:
Blocks:
 
Reported: 2004-08-27 14:32 EDT by Michael J Mole CLA
Modified: 2019-09-06 15:31 EDT (History)
0 users

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 Michael J Mole CLA 2004-08-27 14:32:47 EDT 
Edit box and scroll bar context menus do not have self documented keyboard 
shortcuts.  (i.e. Copy does not show CTRL+C, Cut does not show CTRL+X, etc.)
To reach the context menu, simply right click on any edit box and any scroll 
bar.
Comment 1 Douglas Pollock CLA 2004-08-31 13:50:25 EDT 
Where?
Comment 2 Michael J Mole CLA 2004-09-07 11:53:51 EDT 
If you enter any dialog that contains an edit box, right clicking on the edit
box will bring up the appropriate context menu.  (This issue is consistent
across the all of Eclipse.)
Comment 3 Douglas Pollock CLA 2004-11-04 16:57:38 EST 
I believe these menus are constructed at the native layer.  If someone can 
provide a patch for this, I'd be interested in seeing it.
Comment 4 Michael Van Meekeren CLA 2006-04-21 13:14:17 EDT 
Moving Dougs bugs
Comment 5 Paul Webster CLA 2006-09-28 11:00:29 EDT 
There are currently no plans to work on this feature.

PW
Comment 6 Denis Roy CLA 2007-06-22 09:32:41 EDT 
Changes requested on bug 193523
Comment 7 Eclipse Webmaster CLA 2019-09-06 15:31:12 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.