Florian Müllner b1dd746443 network: Keep key focus in dialog when removing networks ... When the actor that has the key focus is destroyed, Clutter moves the focus to the stage. In case the destroyed actor was inside a ModalDialog, this breaks any keyboard interaction: keynav is broken because the stage isn't in any focus chain, and access keys like Escape because they are handled on the dialog's parent. The only dialog that may destroy a child without recreating the dialog buttons (and thus moving the key focus there) is the WirelessDialog, fix it by keeping the key focus within the dialog when removing networks from the list. https://gitlab.gnome.org/GNOME/gnome-shell/issues/76		2018-05-31 11:42:14 +00:00
..
accessibility.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
bluetooth.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
brightness.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
keyboard.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
location.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
network.js	network: Keep key focus in dialog when removing networks	2018-05-31 11:42:14 +00:00
nightLight.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
power.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
rfkill.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
screencast.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
system.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
thunderbolt.js	thunderbolt: sync D-Bus API with bolt changes	2018-04-20 11:36:37 +02:00
volume.js	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00