Bug 1273786

Summary:	Could not access items correctly in secondary menu using keyboard
Product:	OKD	Reporter:	Yadan Pei <yapei>
Component:	Management Console	Assignee:	Jessica Forrester <jforrest>
Status:	CLOSED NOTABUG	QA Contact:	Yadan Pei <yapei>
Severity:	low	Docs Contact:
Priority:	medium
Version:	3.x	CC:	aos-bugs, mmccomas
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-10-22 02:58:45 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Yadan Pei 2015-10-21 08:41:13 UTC

Description of problem:
Hover or click 'Browse', a pop menu will appear, using 'right' arrow didn't enter the sub-menu, also sometimes 'up' and 'down' arrow didn't work as expected

Version-Release number of selected component (if applicable):
oc v1.0.6-803-g7c12c7a
kubernetes v1.2.0-alpha.1-1107-g4c8e6f4


How reproducible:
Always

Steps to Reproduce:
1.Create an application
2.Check Builds,Deployments,Events,Pods,ImageStreams,Route,Services in 'Browse' by keyboard

Actual results:
Couldn't access the pop menu using 'right' arrow, and keyboard selection among the menu items doesn't work well

Expected results:
Could access the pop menu and able to select different items

Additional info:

Comment 1 Jessica Forrester 2015-10-21 13:04:22 UTC

If you are accessing the primary menu with the keyboard by tabbing through the elements, using the Enter key on the Browse button opens the secondary menu, you can then tab through all the elements in the secondary menu.

We might want to auto-focus the first link in the secondary menu after it opens if it opened as the result of a keyboard event.

Comment 2 Yadan Pei 2015-10-22 02:58:45 UTC

Used wrong keyboard to access

Verified with correct keyboard, the function works well on Firefox,Chrome and Safari, will close the bug