gtkfilechooser save/save as dialog not 100% navigable by keyboard

Bug #388289 reported by Jake Tolbert
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
GTK+
New
Undecided
Unassigned
One Hundred Papercuts
Invalid
Undecided
Unassigned
gtk+2.0 (Ubuntu)
Invalid
Low
Ubuntu Desktop Bugs

Bug Description

When saving a file, the save/save as dialog does not offer any obvious options to select the file format drop down, making navigation of this dialog purely with the keyboard almost impossible.

Several other bugs are related to this keyboard navigation issue (Bug #387957 and Bug #54950, for example), but here, I take issue with the lack of usability in providing an (obvious) hotkey.

Tags: papercut
Changed in gtk+2.0 (Ubuntu):
importance: Undecided → Low
Revision history for this message
Sebastien Bacher (seb128) wrote :

thank you for your bug report, you can switch between widgets using <tab> as in any gtk software

Changed in gtk+2.0 (Ubuntu):
status: New → Incomplete
Revision history for this message
Sebastien Bacher (seb128) wrote :

could you give details on what else behaviour you would expect?

Revision history for this message
Jake Tolbert (crazybilly) wrote :

I was primarily thinking of a alt+x mneomic-style hotkey, which for the most part, is unavailable.

I just opened a few gtk programs to see if I could nail down exactly what I'm thinking of. In a few of them (OO.write and Gimp, for example), there IS a mnemonic hotkey for "Select File Type". Other program's "save as" dialog only have a drop-down menu widget for which there doesn't seem to be a mnemonic (Firefox and Gedit, for example). Unfortunately, while hitting alt+t to focus on that dialog does open the dialog, it doesn't FOCUS it. You have to either hit tab several times or use the mouse.

My goal is to navigate the entire dialog via keyboard in the most efficient manner possible, which would mean a mnemonic that focuses the dialog or focuses/opens the drop-down menu, depending on which is available. I tend to think it should consistently be one or another, but that's only my (uninformed) opinion and certainly out of the scope of this bug report.

Let me know as far as any testing or reporting I can provide! Thanks for your hard work!

Revision history for this message
Sebastien Bacher (seb128) wrote :

The request is rather an upstream one and it would be nice if somebody who has an opinion about the it could send the bug the to the people writting the software (https://wiki.ubuntu.com/Bugs/Upstream/GNOME)

Changed in gtk+2.0 (Ubuntu):
assignee: nobody → Ubuntu Desktop Bugs (desktop-bugs)
status: Incomplete → New
Revision history for this message
The Wind Blows (zachanimerulz) wrote :

My bug report is similar, though I added a different suggestion for close this cut based on what reasoning there was to keep this behavior.
https://bugs.edge.launchpad.net/hundredpapercuts/+bug/487976

Revision history for this message
Vish (vish) wrote :

This bug is an upstream one and it would be quite helpful if somebody experiencing it could send the bug the to the people writing the software. You can learn more about how to do this for various upstreams at https://wiki.ubuntu.com/Bugs/Upstream. Thanks in advance!

Changed in gtk+2.0 (Ubuntu):
status: New → Confirmed
Revision history for this message
Andrea Piccinelli (frasten) wrote :

Here is the upstream bug: https://bugzilla.gnome.org/show_bug.cgi?id=402349 and there you can find an attached patch that should fix the issue. Can somebody test it?

Revision history for this message
Andrea Piccinelli (frasten) wrote :

Sorry, I posted in the wrong bug. Please delete my previous comment.

Revision history for this message
Omer Akram (om26er) wrote :

Are there any news about this bug? Has someone affected by this bug sent the report upstream? May you tell us the bug number? Thanks in advance.

Changed in gtk+2.0 (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Omer Akram (om26er) wrote :

Is this still an issue with current lucid? If so please let us know with specific steps to reproduce so that we could send this bug upstream

Changed in hundredpapercuts:
status: New → Incomplete
Revision history for this message
Chris Wilson (notgary-deactivatedaccount) wrote :

Since there has been no activity on this report since 2010-05-02, it is being closed. If anyone is able to provide the information requested in comment #10, the please feel free to reopen it.

Changed in hundredpapercuts:
status: Incomplete → Invalid
Changed in gtk+2.0 (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.