Red Hat Bugzilla – Bug 863565
Subscription Registration Doesn't Give Focus to Login Field
Last modified: 2013-01-07 23:04:05 EST
Description of problem:
When we move to the Subscription Registration credentials section, we don't give focus to the Login field, the user has to tab or click on it before they can start typing. We should give the field focus when we show that dialog so that the user can instead just start typing, hands planted firmly on the keyboard.
This definitely affects firstboot, but it may affect the dialog when launched from the GUI as well.
This gets a little tricky, since we seem to preserve cursor position between screens during the same session, so you have to close it out and start over to try it fresh.
This request was evaluated by Red Hat Product Management for inclusion
in a Red Hat Enterprise Linux release. Product Management has
requested further review of this request by Red Hat Engineering, for
potential inclusion in a Red Hat Enterprise Linux release for currently
deployed products. This request is not yet committed for inclusion in
Forgot to include this is with a build from today in both RHEL 5 & 6:
Created attachment 626290 [details]
Keyboard focus defaults to the Login field.
[root@jsefler-rhel59 ~]# rpm -q subscription-manager-gui
From within the subscription-manager-gui, manual testing proved that every time the credentials dialog is now opened, the focus goes to the Login: field. If the entered credentials are bad, then this dialog is re-opened with the user's entered data and the Login field is given focus with the value selected.
Created attachment 626299 [details]
Keyboard focus defaults to the Login field. (firstboot)
[root@jsefler-rhel59 ~]# rpm -q subscription-manager-firstboot
From within subscription-manager-firstboot, manual testing proved that every time the credentials firstboot panel is now opened, the focus goes to the Login: field. If the entered credentials are bad, then the focus returns to the Login field with the value entered by the user in a selected state.
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.