gnome-3-28 : lp:metacity : Git : Code : Metacity

Get this branch:: git clone -b gnome-3-28 https://git.launchpad.net/metacity

Branch merges

Branch information

Name:: gnome-3-28

Repository:: lp:metacity

Recent commits

9956d37... by Owen Taylor on 2013-12-16

fix problems with focus tracking

When a client spontaneously focuses their window, perhaps in response
to WM_TAKE_FOCUS we'll get a FocusOut/FocusIn pair with same serial.
Updating display->focus_serial in response to FocusOut then was causing
us to ignore FocusIn and think that the focus was not on any window.

We need to distinguish this spontaneous case from the case where we
set the focus ourselves - when we set the focus ourselves, we're careful
to combine the SetFocus with a property change so that we know definitively
what focus events we have already accounted for.

https://bugzilla.gnome.org/show_bug.cgi?id=720558

b96341d... by Alberts Muktupāvels on 2018-09-08

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

e18f850... by wsxy162 on 2018-03-24