Bug 84251 - On RHN-registration page, keyboard traversal never reaches "Forward" button
On RHN-registration page, keyboard traversal never reaches "Forward" button
Status: CLOSED DUPLICATE of bug 70387
Product: Red Hat Linux
Classification: Retired
Component: up2date (Show other bugs)
8.0
i386 Linux
medium Severity low
: ---
: ---
Assigned To: Adrian Likins
Fanny Augustin
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2003-02-13 14:19 EST by Glen A. Foster
Modified: 2007-04-18 12:51 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2006-02-21 13:51:47 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Glen A. Foster 2003-02-13 14:19:22 EST
Description of problem: I realize keyboard traversal is not an overriding 
design goal for many GUI pages -- but a lot of good work _has_ been done and 
there's currently a glitch in the keyboard traversal mechanism on the page 
where on enters their RHN user name, password, etc.

If you press TAB repeatedly to move the "Enter-key target" from one widget to 
another... all the widgets _except_ the "Forward" key are eventually selected.
It seems the Forward key isn't in the list of widgets to traverse.

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

How reproducible: 100% (always)

Steps to Reproduce:
1. Install 8.0
2. reboot into firstboot
3. say "yes" to "register with RHN?"
4. on the page with username, password, etc., traverse the widgets using the 
TAB key
5. notice that the Forward button is never highlighted/selected.
Comment 1 Adrian Likins 2003-02-13 15:03:11 EST

*** This bug has been marked as a duplicate of 70387 ***
Comment 2 Red Hat Bugzilla 2006-02-21 13:51:47 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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