<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#c10">Comment # 10</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#c7">comment #7</a>) > (In reply to Marc-Andre Lureau from <a href="show_bug.cgi?id=93249#c6">comment #6</a>) > > (In reply to Zeeshan Ali from <a href="show_bug.cgi?id=93249#c5">comment #5</a>) > > > > It would be very unconvenient to explicitely take the grab in order > > > > to give input to this widget. > > > > > > Seems you are talking about the opposite. I'm talking about the state of > > > user explicitly ungrabbing kbd using Ctrl_L+Alt_L keys and then expecting > > > all key event to go to client/host while kbd is ungrabbed. At the very least > > > they should have a way to focus another widget using 'Tab' key. > > > > Probably not. Ungrabbing is for special keys, and tab is not special. > > Well I think it should not be for special keys only. We tell user that > keyboard is ungrabbed, which is already a bit cryptic. Now I really don't > want to explain to them that we only mean special keys cause that's what > SPICE want to mean by ungrabbing. Also: * SPICE docs mention nothing about keyboard ungrab/grab being specific to special keys/combos. * As user of spice-gtk API, I would expect keyboard ungrab to be not very different from mouse ungrab. Since mouse ungrab means all mouse events going to host/client, I don't see why keyboard grab should work any differently.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>