<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - key event going to display even with keyboard ungrabbed" href="https://bugs.freedesktop.org/show_bug.cgi?id=93249#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - key event going to display even with keyboard ungrabbed" href="https://bugs.freedesktop.org/show_bug.cgi?id=93249">bug 93249</a> from <a class="email" href="mailto:zeenix@gmail.com" title="Zeeshan Ali <zeenix@gmail.com>"> Zeeshan Ali</a> <pre>(In reply to Zeeshan Ali from <a href="show_bug.cgi?id=93249#c17">comment #17</a>) > (In reply to Victor Toso from <a href="show_bug.cgi?id=93249#c16">comment #16</a>) > > (In reply to Christophe Fergeau from <a href="show_bug.cgi?id=93249#c14">comment #14</a>) > > > (In reply to Jonathon Jongsma from <a href="show_bug.cgi?id=93249#c13">comment #13</a>) > > > > (In reply to Victor Toso from <a href="show_bug.cgi?id=93249#c11">comment #11</a>) > > > > > IMHO, if the user does not want the key to go to boxes after ctrl_l+alt_l he > > > > > should switch the focus to the target app, where they key should go. > > > > > (ctrl_l+alt_l then alt+tab works with remote-viewer here) > > > > > > > > > > > > Well, as far as I know, it's also important for accessibility within the > > > > application itself, not just between different apps. But it works for me > > > > here as well. And not just Alt+tab. If I release the grab in virt-viewer (by > > > > pressing ctrl_l+alt_l), I can now press Alt+F and the virt-viewer "file" > > > > menu opens. So that seems to be the behavior Zeeshan was requesting. > > > > > > My understanding is that this indeed is all about what happens after the > > > ungrab combo is pressed (see > > > <a href="http://cgit.freedesktop.org/spice/spice-gtk/commit/">http://cgit.freedesktop.org/spice/spice-gtk/commit/</a> > > > ?id=767e5522f64c115f66f6419abd378ad568e5564e ). After the combo has been > > > pressed, I'd expect all keys to go to the client rather than the guest until > > > the mouse moves (or is clicked?), or until the combo is pressed again. > > > > Pavel's commit mentions exactly for keyboard shortcuts after ungrab combo. > > > > If we change the behavior to ignore any keyboard input after ungrab combo, > > it might be the case that user's typing will be lost till he realize that he > > must move the mouse or do the UNgrab combo to grab it. > > * Apps can help with that. E.g Boxes already shows a label in topbar and we > could grey out/disable the guest display widget or replace it with another > widget when keyboard is ungrabbed. There are many things that could be done > to ensure user knows keyboard is currently grabbed. BTW, SPICE could handle that as well and IMO it probably should but I'm happy if this bug is fixed and won't want to push my luck. :)</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>