Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 353626 - Bad command / key binding enablement in Quick Access field
Summary: Bad command / key binding enablement in Quick Access field
Status: CLOSED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 4.2   Edit
Hardware: All All
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Platform UI Triaged CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
: 386803 (view as bug list)
Depends on:
Blocks:
 
Reported: 2011-08-02 13:27 EDT by Markus Keller CLA
Modified: 2019-11-27 07:11 EST (History)
6 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Markus Keller CLA 2011-08-02 13:27:14 EDT
I20110729-0200 (4.2)

- open an editor
- press Command+3 or click into the Quick Access field
- press Command+F12 to activate the editor again
=> does nothing

Activate Editor works fine if the editor didn't have focus before.

I think the quick access control needs to be treated as separate part when it comes to keyboard activation. Currently, it steals the editor's focus but leaves editor actions active: E.g. Option+Shift+Left/Right extends the selection in the editor.

Even worse, Option+Up/Down moves a line in the editor.
Comment 1 Dani Megert CLA 2011-08-03 02:28:17 EDT
Same on Windows 7 but with F12 instead of Command+F12.
Comment 2 Brian de Alwis CLA 2014-08-21 11:08:44 EDT
*** Bug 386803 has been marked as a duplicate of this bug. ***
Comment 3 Brian de Alwis CLA 2014-08-21 12:21:39 EDT
This binding issue becomes particularly annoying with single-character keybindings (e.g., "g" in an non-textual parts).  I'm guessing this problem exists with any text field in a workbench tool contribution.

It looks similar to the workaround in bug 346390.  There, in #346390c4, Paul wrote:
> In Eclipse 4 the architecturally correct solution would look like creating an
> IEclipseContext for that control and making it the active child of the Window
> context while that control is active.  But that effects which handlers are
> enabled/disabled, what is the active part, and I'm not sure what that does to 
> the available commands listed in the quick assist drop down.
Comment 4 Lars Vogel CLA 2019-11-27 07:11:38 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.