Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.

Bug 339044

Summary: [KeyBindings] Key bindings with Ctrl+Shift+... fail in browser
Product: [Eclipse Project] Platform Reporter: Stefan Mücke <s.muecke>
Component: UIAssignee: Platform UI Triaged <platform-ui-triaged>
Status: CLOSED WONTFIX QA Contact:
Severity: normal    
Priority: P3 CC: prakash, remy.suen
Version: 3.7   
Target Milestone: ---   
Hardware: PC   
OS: Windows 7   
Whiteboard: stalebug

Description Stefan Mücke CLA 2011-03-06 18:38:21 EST
Build id: I20110127-2034 (Eclipse 3.7 M5)

Steps to reproduce:

1.  Add key binding 'Ctrl+T' to command 'Open Resource'
2.  Open the internal Browser editor and navigate to a page
    (e.g. via Quick Access: Ctrl+3 --> Command 'Open Browser')
3.  Click the web page to give the browser widget the focus
4.  Hit 'Ctrl+Shift+T' to invoke the 'Open Type' dialog
    Result: The 'Open Resource' dialog is opened instead.

In Eclipse 3.6, hitting Ctrl+Shift+T repeatedly will open
the two dialogs alternately. In Eclipse 3.7 M5, the 'Shift' key
is never honored and always 'Open Resource' is opened.

I have tried the following debug options:

org.eclipse.ui/debug=true
org.eclipse.ui/trace/keyBindings=true
org.eclipse.ui/trace/keyBindings.verbose=true

Among the console output is the following line:

KEYS >>> WorkbenchKeyboard.press(potentialKeyStrokes = [CTRL+SHIFT+, CTRL+T, CTRL+SHIFT+T])

Note that CTRL+T is listed before CTRL+SHIFT+T. When hitting Ctrl+Shift+T in another view or editor, however, the output is only:

KEYS >>> WorkbenchKeyboard.press(potentialKeyStrokes = [CTRL+SHIFT+T])
Comment 1 Prakash Rangaraj CLA 2011-03-07 05:30:54 EST
Paul,
       Were there any changes in WorkbenchKeyboard or this is potentially a SWT bug?
Comment 2 Lars Vogel CLA 2019-11-08 04:36:32 EST
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.

If the bug is still relevant please remove the stalebug whiteboard tag.