GNOME Bugzilla – Bug 88853
Panel does not receive focus after Properties dialog
Last modified: 2004-12-22 21:47:04 UTC
I move focus to an object, e,g, a drawer on a panel (Ctrl+Alt+Tab to get focus on the panel and then Tab to move focus along the panel) and then press Shift+F10 to display the context menu. I press Down arrow and then Spacebar to activate the Properties dialog. When the dialog is closed another window receives focus instead of the panel. It seems desirable that the panel would receives focus.
This is minor, right, calum? (i.e., you can always ctl+alt+tab again, right?)
Well, it's probably not a stopper, but it's pretty annoying and does break the user's fundamental expectations of dialog boxes (that is, when you close one, focus goes back to where it was before).
Probably if you close a dialog, its transient parent should be focused rather than the topmost window. (Though most of the time these will coincide, the panel doesn't count in "topmost window" calculations so it doesn't for the panel case.) Then the remaining bug will be that the panel doesn't set the transient hints for its dialogs... we could catch that by always focusing topmost window of the application the dialog belonged to.
This commit is intended to fix this but doesn't work for some reason: 2002-09-27 Havoc Pennington <hp@pobox.com> * src/screen.c (meta_screen_focus_top_window): raise the focused window, since it may not be the window on top, given the below change. * src/stack.c (meta_stack_get_default_focus_window): make this more complex to prefer to focus the transient parent, followed by other windows in group, followed by topmost non-dock, followed by dock. Previously was just topmost non-dock followed by dock ignoring groups and transiency.
currently the focus_top_window stuff is even more hosed than it was before, due to the hack for mouse focus mode where it checks current pointer position instead.
Updating status_whiteboard field to reflect A11Y team's assessment of accessibility impact.
Apologies for spam... marking as GNOMEVER2.3 so it appears on the official GNOME bug list :)
This bugs is not reproducible with metacity from CVS HEAD.