<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [wayland] Gtk4 API - add an api for shortcut inhibitor since individual device grabs shall/should probably go" href="https://bugzilla.gnome.org/show_bug.cgi?id=791057#c2">Comment # 2</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [wayland] Gtk4 API - add an api for shortcut inhibitor since individual device grabs shall/should probably go" href="https://bugzilla.gnome.org/show_bug.cgi?id=791057">bug 791057</a> from <a href="page.cgi?id=describeuser.html&login=ofourdan%40redhat.com" title="Olivier Fourdan <ofourdan@redhat.com>"> Olivier Fourdan</a> <pre>Created <a href="attachment.cgi?id=366883&action=diff" name="attach_366883" title="[PATCH] gdk: Add GDK_SEAT_CAPABILITY_KEYBOARD_SHORTCUTS">attachment 366883</a> <a href="attachment.cgi?id=366883&action=edit" title="[PATCH] gdk: Add GDK_SEAT_CAPABILITY_KEYBOARD_SHORTCUTS">[details]</a> <a href='review?bug=791057&attachment=366883'>[review]</a> [PATCH] gdk: Add GDK_SEAT_CAPABILITY_KEYBOARD_SHORTCUTS Instead of trying to come up with random heuristics to the existing grab API as to when to issue a shortcut inhibition request on Wayland, add a new virtual capability GDK_SEAT_CAPABILITY_KEYBOARD_SHORTCUTS. This capability is reported only on Wayland for keyboard devices when the Wayland compositor supports the shortcut inhibitor protocol. This way, applications can tell whether the Wayland compositor supports the shortcut inhibitor protocol, and use it along their seat grabs when intended.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>