fa4a787386
The keyboard accessibility setting "enable" is actually even more misleading that initially anticipated, as it does not control the entire keyboard accessibility feature, but just the "enable by keyboard" feature, i.e. being able to enable or disable stickykeys or slowkeys using various keyboard actions. Yet the accessibility features should still work even if the "enable" setting is unset, those can be controlled by the accessibility menu in GNOME Shell for example. Change the clutter/evdev implementation to match that behavior as found in the x11 backend, so both backends are now consistent. https://gitlab.gnome.org/GNOME/mutter/merge_requests/531 |
||
|---|---|---|
| .. | ||
| clutter | ||
| tests | ||
| .gitignore | ||
| meson.build | ||