https://bugs.documentfoundation.org/show_bug.cgi?id=166579
Buovjaga <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Blocks| |103182, 100156 --- Comment #11 from Buovjaga <[email protected]> --- Code pointer: vcl/unx/gtk3/gtkframe.cxx KeyIndicatorState GtkSalFrame::GetIndicatorState() { KeyIndicatorState nState = KeyIndicatorState::NONE; #if !GTK_CHECK_VERSION(4, 0, 0) GdkKeymap *pKeyMap = gdk_keymap_get_for_display(getGdkDisplay()); if (gdk_keymap_get_caps_lock_state(pKeyMap)) nState |= KeyIndicatorState::CAPSLOCK; if (gdk_keymap_get_num_lock_state(pKeyMap)) nState |= KeyIndicatorState::NUMLOCK; if (gdk_keymap_get_scroll_lock_state(pKeyMap)) nState |= KeyIndicatorState::SCROLLLOCK; #endif return nState; } https://docs.gtk.org/gdk3/method.Keymap.get_scroll_lock_state.html I cloned the gtk-3-24 branch like so in order to investigate: git clone --depth=1 --branch gtk-3-24 https://gitlab.gnome.org/GNOME/gtk.git https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/gdk/gdkkeys.c /** * gdk_keymap_get_scroll_lock_state: * @keymap: a #GdkKeymap * * Returns whether the Scroll Lock modifer is locked. * * Returns: %TRUE if Scroll Lock is on * * Since: 3.18 */ gboolean gdk_keymap_get_scroll_lock_state (GdkKeymap *keymap) { g_return_val_if_fail (GDK_IS_KEYMAP (keymap), FALSE); return GDK_KEYMAP_GET_CLASS (keymap)->get_scroll_lock_state (keymap); } https://gitlab.gnome.org/GNOME/gtk/-/blob/gtk-3-24/gdk/wayland/gdkkeys-wayland.c static gboolean gdk_wayland_keymap_get_scroll_lock_state (GdkKeymap *keymap) { return xkb_state_led_name_is_active (GDK_WAYLAND_KEYMAP (keymap)->xkb_state, XKB_LED_NAME_SCROLL); } So gtk indeed seems to be watching the LED specifically. Referenced Bugs: https://bugs.documentfoundation.org/show_bug.cgi?id=100156 [Bug 100156] [META] Wayland-related bugs https://bugs.documentfoundation.org/show_bug.cgi?id=103182 [Bug 103182] [META] GTK3-specific bugs -- You are receiving this mail because: You are the assignee for the bug.
