Bug 1073370 - [RFE] [UI]: WebAdmin does not support keyboard navigation/shortcuts
Summary: [RFE] [UI]: WebAdmin does not support keyboard navigation/shortcuts
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Frontend.WebAdmin
Version: 3.4.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Alexander Wels
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On: ovirt_ui_redesign
Blocks: 1505904
TreeView+ depends on / blocked
 
Reported: 2014-03-06 10:12 UTC by Ilanit Stein
Modified: 2019-04-28 14:14 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
This update adds the ability to navigate between objects of the same type by using the Up and Down keys. For example, while viewing a virtual machine, press Up to go to the previous virtual machine.
Clone Of:
Environment:
Last Closed: 2017-12-20 11:20:34 UTC
oVirt Team: UX
Embargoed:
rule-engine: ovirt-4.2+
gklein: testing_plan_complete+
mgoldboi: planning_ack+
oourfali: devel_ack+
pstehlik: testing_ack+


Attachments (Terms of Use)
screen-cast: current behavior of up/down keyboard arrows (1.98 MB, video/ogg)
2014-05-15 15:17 UTC, Einav Cohen
no flags Details

Description Ilanit Stein 2014-03-06 10:12:10 UTC
Description of problem:
At all system tabs: VMs, templates, storage, events, etc,
no response to keyboard press. for example no option to scroll using up/down arrows, no option to delete a component  

Version-Release number of selected component (if applicable):
av2

Comment 1 Ilanit Stein 2014-03-06 11:02:41 UTC
The problem see on firefox 17.0.0

Comment 2 Einav Cohen 2014-05-15 15:17:11 UTC
Created attachment 895973 [details]
screen-cast: current behavior of up/down keyboard arrows

Comment 3 Einav Cohen 2014-05-15 15:19:28 UTC
this is indeed a regression from the WPF client (RHEV-3.0). However, once we moved to a web-based client, things have changed and we need to re-think about the correct behavior. 

example: in the WPF, if you had a selected item, clicking on the up/down arrows changed the select item to be the one located one row above/below the originally selected item. 
now, in the web-based GUI, if you are selecting an item, clicking on the up/down arrows will scroll the grid view, rather than change the selection (see attachment 895973 [details]). 

which behavior is more correct? not sure. 

adding the UserExperience Keyword (UXD advice is needed here).

Comment 7 Yaniv Kaul 2015-11-29 08:43:27 UTC
I'm aware it's a regression from the old UI, but having that keyword wakes up the bad bugzilla bot to ask for a blocker flag. And this is not a blocker.
Therefore, removing the regression flag.

Comment 9 Oved Ourfali 2017-05-15 06:37:43 UTC
We will add some keyboard shortcuts in 4.2 as part of the UI re-design.

Comment 10 Red Hat Bugzilla Rules Engine 2017-05-15 06:37:53 UTC
This request has been proposed for two releases. This is invalid flag usage. The ovirt-future release flag has been cleared. If you wish to change the release flag, you must clear one release flag and then set the other release flag to ?.

Comment 11 Lucie Leistnerova 2017-10-24 13:54:05 UTC
Now supported keyboard navigation/shortcuts:

- Navigation via key arrows in VMs detail - changing detail to other VM depending on sort by.
- Shortcut Ctrl+Alt+S for search form in VM detail breadcrumb - search then can be processed by Enter and key arrow goes through the search result. Enter in search result changes the VM detail to the selected one.

At this moment there is no need of other shortcuts, but can be added some. So feel free to open new RFE for the others.

verified in 
ovirt-engine-webadmin-portal-4.2.0-0.0.master.20171023193344.gitc3b23f6.el7.centos.noarch

Comment 12 Sandro Bonazzola 2017-12-20 11:20:34 UTC
This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.