Bug 392623

Summary: Misc keyboard navigation complaints (3 bugs in one report)
Product: [openSUSE] openSUSE 11.0 Reporter: Frank Arnold <frank.arnold>
Component: InstallationAssignee: Stefan Hundhammer <shundhammer>
Status: RESOLVED DUPLICATE QA Contact: Jiri Srain <jsrain>
Severity: Normal    
Priority: P5 - None    
Version: Beta 3   
Target Milestone: ---   
Hardware: Other   
OS: Other   
Whiteboard:
Found By: --- Services Priority:
Business Priority: Blocker: ---
Marketing QA Status: --- IT Deployment: ---

Description Frank Arnold 2008-05-20 14:19:35 UTC
Some usability issues of the installer: 

Seen in Partitioning and Grub Settings section:
Normally, you'll be able to activate different fields or buttons with Alt + accelerator key. This does not work in the mentioned sections. You have to press the key combination twice to get focus on the desired button and then press space or enter to do what you want.

The pattern selection list does not follow the selection bar if it's operated by cursor keys. It scrolls down only when it hits some of the headers displayed in there. This was seen on Beta2. On Beta3 this pane didn't show anything, manual package selection is nearly impossible with it...

The Help button does not have an accelerator.

And the last one: Please try to select the language with cursor keys - this is a plain no go for me. Changing the language each time you press up or down and loading some lang packs off of the CD isn't exactly optimal. I know there are other methods like type ahead or something. Perhaps it's some personal preference from my side, but worth to think about it anyway.

Just try to use the installer without a mouse and you know what I mean... ;)
Comment 1 Stephan Kulow 2008-05-21 20:17:40 UTC
about the last issue: press space to open the popup and then you can select it - on enter it will change the language.

the pattern one is the most ugly in one in my keyboard navigation experience .)
Comment 2 Stefan Hundhammer 2008-06-02 12:19:41 UTC
The first issue is bug #393040 .

*** This bug has been marked as a duplicate of bug 393040 ***