<html> <head> <base href="https://bugzilla.gnome.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - popup windows don't get touch events" href="https://bugzilla.gnome.org/show_bug.cgi?id=750845#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - popup windows don't get touch events" href="https://bugzilla.gnome.org/show_bug.cgi?id=750845">bug 750845</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=312964&action=diff" name="attach_312964" title="wayland: Emulate crossing events when switching between pointer and touch">attachment 312964</a> <a href="attachment.cgi?id=312964&action=edit" title="wayland: Emulate crossing events when switching between pointer and touch">[details]</a> <a href='review?bug=750845&attachment=312964'>[review]</a> wayland: Emulate crossing events when switching between pointer and touch The common GDK code accounts for "pointer emulating" touch sequences to be synchronized with the pointer position by the windowing system. However on Wayland pointer and touch are completely independent, the backend attempts to implement pointer emulation, but doesn't account for the possible crossing events happening when the user switches from pointer to touch or the opposite. This will ensure that window_under_pointer lookups are correct for pointer events emulated out of touch events, and don't end up ignored if the pointer emulating touch sequence and the real pointer lie in different toplevels. Inspired in a former patch by Jonny Lamb <<a href="mailto:jonnylamb@gnome.org">jonnylamb@gnome.org</a>></pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>