Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.

Bug 83133

Summary: TAB cycles onto an invisible element
Product: [Retired] Red Hat Public Beta Reporter: David Balažic <david.balazic>
Component: anacondaAssignee: Jeremy Katz <katzj>
Status: CLOSED WONTFIX QA Contact: Mike McLean <mikem>
Severity: low Docs Contact:
Priority: medium    
Version: phoebe   
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-01-31 02:53:32 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description David Balažic 2003-01-30 16:26:58 UTC
Description of problem:

When install is started with "linux text noprobe" and the "Devices" window 
appears, it has two buttons : "Done" and "Add Device"

None of them is selected. By using <TAB>, one can cycle thru them, but a third 
invisible element is also part of the cycle :

[Done] --TAB--> [Add Device] --TAB--> something_invisible --TAB---\
  ^                                                               |
  |                                                               |

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

How reproducible:

Steps to Reproduce:
1. boot with : linux text noprobe
2. in the "devices" windows press TAB several times
Actual results:
selection cycles thru the two buttons and a third invisible element

Expected results:
Should only cycle thru the two buttons.

Additional info:

Comment 1 Jeremy Katz 2003-01-31 02:53:32 UTC
There's a list that just has no items.  This isn't anything new and would
require significant changes (ie not using newtWinMenu) to implement, so is going
to stay this way.