<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - Palm detection on Precision Touchpads causes spurious taps"
href="https://bugs.freedesktop.org/show_bug.cgi?id=106716">106716</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>Palm detection on Precision Touchpads causes spurious taps
</td>
</tr>
<tr>
<th>Product</th>
<td>Wayland
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>All
</td>
</tr>
<tr>
<th>OS</th>
<td>Linux (All)
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>enhancement
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>libinput
</td>
</tr>
<tr>
<th>Assignee</th>
<td>wayland-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mdmayfield@yahoo.com
</td>
</tr></table>
<p>
<div>
<pre>On a Precision Touchpad, the Confidence bit goes to 0 if a touch is determined
not to be a finger by the firmware. For users of Tap-to-click, this means that
a palm resting on the surface of the touchpad causes a click:
1) Palm begins to touch the touchpad
2) Touchpad recognizes the touch and reports it to the kernel with Confidence
bit set
3) Kernel reports the touch to userspace as active
4) Touchpad firmware realizes the touch is a palm and begins reporting
Confidence=0 to the kernel
5) Kernel reports the touch to userspace as inactive
6) Userspace sees this and assumes the user lifted the finger
7) Tap-to-click registers this as a click
This is particularly painful because, while accidental mouse pointer movements
through failed palm detection can be annoying, accidental mouse *clicks* can be
disastrous.
On the LKML I see Dmitry Torokhov submitted this patch to resolve this issue:
<a href="https://lkml.org/lkml/2017/8/10/970">https://lkml.org/lkml/2017/8/10/970</a>
However the last response on that thread I see is from Peter Hutterer a few
days later, with no further decision or action taken by the kernel devs:
<a href="https://lkml.org/lkml/2017/8/17/1072">https://lkml.org/lkml/2017/8/17/1072</a>
Has there been any further communication with the Linux kernel team, or would
it be possible to either handle this in userspace, or follow up to encourage
the kernel developers to revisit this issue?</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>