<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Unreliable tap-to-click on a DELL XPS 9370" href="https://bugs.freedesktop.org/show_bug.cgi?id=106044#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Unreliable tap-to-click on a DELL XPS 9370" href="https://bugs.freedesktop.org/show_bug.cgi?id=106044">bug 106044</a> from <a class="email" href="mailto:peter.hutterer@who-t.net" title="Peter Hutterer <peter.hutterer@who-t.net>"> Peter Hutterer</a> <pre>Problem in this one is the motion, yes. events that matter here: E: 0.992120 0003 0036 0307 # EV_ABS / ABS_MT_POSITION_Y 307 E: 0.999293 0003 0036 0324 # EV_ABS / ABS_MT_POSITION_Y 324 This is a 17 unit movement, translating to a 1.4mm movement. Which is just above the 1.3mm threshold. So yeah, you're just triggering the motion threshold on the first event after touch down, converting the whole thing into pointer motion. That's the source of the issue, I guess there are some heuristics we can improve to make this less of an issue. Note ahead: increasing the motion threshold makes the touchpad less responsive, so that's not ideal either.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>