Carlos Garnacho 702338bc7d keyboardManager: Preserve current keymap across reloads ... The IM can pretty much update the input sources anytime (even if to set the same ones). That ends up triggering rebuilding all user defined keymaps, and losing modifier state if we are unfortunate enough that this caught us while pressing one. One common situation seems to be password entries, resulting in the wrong character being printed if the first character happens to require the shift key. If the current keymap is not found in the newly loaded list, this._current will end up null, with the same behavior as we get currently (immediate keymap reload). https://bugzilla.redhat.com/show_bug.cgi?id=1569211 https://gitlab.gnome.org/GNOME/gnome-shell/issues/240 Closes: #240		2018-04-29 17:52:56 +02:00
..
extensionPrefs	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
gdm	cleanup: Use Function.prototype.bind()	2018-02-21 13:55:02 +00:00
misc	keyboardManager: Preserve current keymap across reloads	2018-04-29 17:52:56 +02: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	polkitAgent: Guard against repeated close() calls	2018-04-21 22:39:15 +02: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