Florian Müllner b3045cb964 closeDialog: Untrack chrome when window loses focus ... On X11, reactive chrome must be added to the input region in order to work as expected. However that region works independently from any window stacking, with the result that the unresponsive-app dialog currently blocks all input in the "covered" area, even in windows stacked above the unresponsive window. The correct fix would be to track the unobscured parts of the dialog and set the input region from that, but that's quite cumbersome. So instead, only track chrome when the corresponding window is focused (or the dialog itself of course). https://gitlab.gnome.org/GNOME/gnome-shell/issues/273		2019-01-24 16:47:33 +01:00
..
extensionPrefs	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
gdm	gdm, util: Always allow to retry login in unlock mode	2018-07-25 20:38:58 +00:00
misc	ibusManager: Don't pass undefined callback to ibus	2019-01-21 16:28:20 +00:00
perf	cleanup: Use arrow notation for anonymous functions	2018-02-21 13:55:00 +00:00
portalHelper	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
ui	closeDialog: Untrack chrome when window loses focus	2019-01-24 16:47:33 +01:00
js-resources.gresource.xml	thunderbolt: add policy provider and indicator	2018-02-05 21:38:49 +01:00
meson.build	build: Support the meson build system	2017-07-20 00:20:54 +02:00