Bug 528960 - Support keyboard-only navigation (usability)
Summary: Support keyboard-only navigation (usability)
Status: CLOSED MOVED
Alias: None
Product: ECP
Classification: Modeling
Component: EMF Forms (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: 2.0.0   Edit
Assignee: Eugen Neufeld CLA
QA Contact:
URL:
Whiteboard: stalebug
Keywords:
Depends on:
Blocks:
 
Reported: 2017-12-19 10:38 EST by Mat Hansen CLA
Modified: 2024-02-28 12:54 EST (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mat Hansen CLA 2017-12-19 10:38:15 EST
Currently is pretty much impossible to navigate and work with an EMFForms view using keyboard navigation only. This can be very frustrating for power users. In my opinion, we lack the following features to support a coherent keyboard navigation experience:

- setting a default focus control which gets the initial focus when the view is rendered the first time
- the configuration of a custom tab order (which needs to be nested for sub-controls like the table view)
- focus highlighting support, right now it is very difficult if not impossible to visually identify the control which has the focus (might also be a theming issue)
- shortcuts for toggling helper popups like the date picker
- action shortcuts (like adding/removing entries to/from a tree/table)
- consistent keybindings for changing the selection within trees, tables, categorizations etc.

In our makeithappen demo, for example, the user is stuck right after opening the DateTimeControlRenderer popup, even when closing it using the mouse tabbing out does not work either.

We probably would need to provide some framework support to support those use-cases within custom controls as well. Finally, it would be nice if the user could easy overwrite those keybindings using some sort of registry.
Comment 1 Eclipse Genie CLA 2020-01-17 16:16:52 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.

--
The automated Eclipse Genie.
Comment 2 Eclipse Genie CLA 2022-01-07 15:15:28 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.

--
The automated Eclipse Genie.
Comment 3 Eclipse Genie CLA 2023-12-29 14:48:21 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.

--
The automated Eclipse Genie.
Comment 4 Eclipse Webmaster CLA 2024-02-28 12:54:46 EST
This issue has been migrated to https://api.github.com/eclipse-ecp/issues/org.eclipse.emf.ecp.core.