diff options
| author | Samuel Thibault <[email protected]> | 2018-08-30 18:11:29 +0200 |
|---|---|---|
| committer | Colomban Wendling <[email protected]> | 2018-10-17 18:12:37 +0200 |
| commit | cdaf08f254981d920918fcfdb1aa356dfdf66306 (patch) | |
| tree | 03acfd5226bdf7adbe1df74372364f0e4794214e /help/mate-clock/zh_CN | |
| parent | d9dcf9c2166b24677994ff1efe938e16c33c4b6c (diff) | |
| download | mate-panel-cdaf08f254981d920918fcfdb1aa356dfdf66306.tar.bz2 mate-panel-cdaf08f254981d920918fcfdb1aa356dfdf66306.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
This a backport of commit f0f4c5e1217eefd46edf9f98633fb32967c67461.
Diffstat (limited to 'help/mate-clock/zh_CN')
0 files changed, 0 insertions, 0 deletions