summaryrefslogtreecommitdiff
path: root/HACKING
diff options
context:
space:
mode:
authorAlberts Muktupāvels <alberts.muktupavels@gmail.com>2018-09-08 18:24:42 +0300
committerAlberts Muktupāvels <alberts.muktupavels@gmail.com>2018-09-10 13:38:13 +0300
commitb96341dabffc3589520343ef0b5590945a67a736 (patch)
tree2793c941082c11c58800d65db4ed57b9fee42aa7 /HACKING
parente18f850c461bd4081df91751e74fe401b6d80f31 (diff)
downloadmetacity-b96341dabffc3589520343ef0b5590945a67a736.tar.gz
display: ensure that we ignore our own focus events for focus predictions
When we set the input focus, we first set the predicted window, and then try to process focus events. But as FocusOut on the existing window comes before FocusIn on the new window, we'll see the focus out on the old window and think the focus is going to nothing, which makes metacity think the prediction failed. Fix this by making sure that we ignore focus window changes of our own cause when updating the focus window field, by ignoring all focus events that have a serial the same as the focus request or lower. Note that if metacity doens't make any requests after the focus request, this could be racy, as another client could steal the focus, but metacity would ignore it as the serial was the same. Bump the serial by making a dummy ChangeProperty request to a metactiy-controlled window in this case. Based on mutter commit: https://gitlab.gnome.org/GNOME/mutter/commit/7fdfbad6d495ede1632588e528801443846e5f6d
Diffstat (limited to 'HACKING')
0 files changed, 0 insertions, 0 deletions