gnome-shell/js
Florian Müllner 7190666075 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
2018-10-08 16:03:53 +00:00
..
extensionPrefs dbus: Move all interface descriptions into the resource 2018-09-17 07:34:49 +00:00
gdm dbus: Move all interface descriptions into the resource 2018-09-17 07:34:49 +00:00
misc inputMethod: Fix setting surrounding text 2018-10-04 16:33:12 +00:00
perf scripting: Fix argument list of createTestWindow() 2018-04-25 23:47:06 +02:00
portalHelper dbus: Move all interface descriptions into the resource 2018-09-17 07:34:49 +00:00
ui closeDialog: Untrack chrome when window loses focus 2018-10-08 16:03:53 +00:00
js-resources.gresource.xml build: Use dedicated resources for helper programs 2018-08-14 17:28:04 +00:00
meson.build build: Use dedicated resources for helper programs 2018-08-14 17:28:04 +00:00
portal-resources.gresource.xml dbus: Move all interface descriptions into the resource 2018-09-17 07:34:49 +00:00
prefs-resources.gresource.xml build: Use dedicated resources for helper programs 2018-08-14 17:28:04 +00:00