Bug 1304280

Summary:	<Tab> key doesn't go to "Cancel" button on contract selection window
Product:	Red Hat Enterprise Linux 6	Reporter:	Rehana <redakkan>
Component:	subscription-manager	Assignee:	William Poteat <wpoteat>
Status:	CLOSED ERRATA	QA Contact:	John Sefler <jsefler>
Severity:	low	Docs Contact:
Priority:	medium
Version:	6.8	CC:	bcourt, csnyder, wpoteat
Target Milestone:	rc	Keywords:	Triaged
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-05-10 20:40:14 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 Rehana 2016-02-03 09:03:43 UTC

Description of problem:
Observed that the tab key doesnt select the "Cancel" button the the contract selection window

Version-Release number of selected component (if applicable):
subscription management server: 0.9.51.15-1
subscription management rules: 5.15.1
subscription-manager: 1.16.8-1.el6
python-rhsm: 1.16.6-1.el6


How reproducible:
Always

Steps to Reproduce:
1.Register the system
2.Click update on "All available subscriptions" tab
3.Select a subscription that has multiple contracts associated with it --> Click Attach
4.Now press <Tab> to select the "cancel"button

Actual results:
Observed that the "cancel" is not getting selected

Expected results:
User should be able to navigate on the contract selection window with tab key , and the cancel button should be selected by the key

Additional info:

Comment 4 Rehana 2016-02-24 09:31:54 UTC

Retested with, 

subscription-manager: 1.16.8-3.el6
python-rhsm: 1.16.6-1.el6


User  is now able to navigate on the contract selection window with tab key , and select the "cancel" button 

Moving the bug to verified!!

Comment 6 errata-xmlrpc 2016-05-10 20:40:14 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

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

https://rhn.redhat.com/errata/RHBA-2016-0797.html