diff options
| author | Samuel Thibault <[email protected]> | 2018-08-30 18:11:29 +0200 |
|---|---|---|
| committer | lukefromdc <[email protected]> | 2018-09-26 00:18:03 -0400 |
| commit | f0f4c5e1217eefd46edf9f98633fb32967c67461 (patch) | |
| tree | cf66d12ba747544370762d077417409a2064a01d /po/bn_IN.po | |
| parent | 4c30c52e4857da9d23e284aa75b12c8ab62e2ee4 (diff) | |
| download | mate-panel-f0f4c5e1217eefd46edf9f98633fb32967c67461.tar.bz2 mate-panel-f0f4c5e1217eefd46edf9f98633fb32967c67461.tar.xz | |
menu-bar: transfer focus correctly on alt-F1
The background is in https://gitlab.gnome.org/GNOME/gtk/issues/85 . One of
the conclusions, in https://gitlab.gnome.org/GNOME/gtk/issues/85#note_264804
, is that mate-panel needs to properly transfer focus on alt-F1 keyboard
shortcut.
It used to work only by luck before, only because gtk used to
deactivate itself during a keyboard grab. But as discussed in
https://gitlab.gnome.org/GNOME/gtk/issues/85 that behavior poses
accessibility feedback issues, is not coherent, and keyboard grab
feedback will not be available in wayland anyway. Thus @ebassi saying
in https://gitlab.gnome.org/GNOME/gtk/issues/85#note_264804 that not
transferring focus properly is the actual bug.
This change explictly switches to the menu bar after saving which X Window
had the focus, and on menu bar deactivation restores focus to that X Window.
Fixes #851
Diffstat (limited to 'po/bn_IN.po')
0 files changed, 0 insertions, 0 deletions