<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GTK applications crash when using touchscreen" href="https://bugzilla.gnome.org/show_bug.cgi?id=776220#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GTK applications crash when using touchscreen" href="https://bugzilla.gnome.org/show_bug.cgi?id=776220">bug 776220</a> from <a href="page.cgi?id=describeuser.html&login=carlosg%40gnome.org" title="Carlos Garnacho <carlosg@gnome.org>"> Carlos Garnacho</a> <pre>Created <a href="attachment.cgi?id=365834&action=diff" name="attach_365834" title="wayland: Only send full sequences of touch events to clients">attachment 365834</a> <a href="attachment.cgi?id=365834&action=edit" title="wayland: Only send full sequences of touch events to clients">[details]</a> <a href='review?bug=776220&attachment=365834'>[review]</a> wayland: Only send full sequences of touch events to clients If input happens to be grabbed somewhere along the shell, and ungrabbed while a touch operation is ongoing, the wayland bits will happily start sending wl_touch.update events from an undeterminate point, without clients having ever received wl_touch.down for that id. Consider those touches grabbed for the entirety of their lifetime, if wl_touch.down wasn't received by the client, no other events will.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>