[Wayland-bugs] [Bug 103210] One-finger tap registered as two-finger tap when touch-size-based palm rejection is triggered

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=103210

--- Comment #11 from Peter Hutterer <peter.hutterer at who-t.net> ---
(In reply to Peter Y. Chuang from comment #10)
> 2. More of the times it doesn't work. In fact, taps don't work even well
> after typing has ended *and* the palm is lifted. In this scenario,
> tap-to-click doesn't recover until I type for a bit with my palm *off*.
> After that, it works again after a tap or two, I think.

I really need something reproducible here or some pattern that we suspect. It's
a bit tricky to write test cases otherwise. I suspect you're hitting one state
where we don't recover correctly, but I don't quite know which one it is yet.

> Regarding the typing-with-palm-off-then-palm-on scenario, I think it depends
> on how quickly you put your palm on the touchpad after finishing typing. I'd
> say tapping works if I put my palm on the touchpad about a second after the
> typing has ended. But if the palm is put on the touchpad *immediately* after
> the last keystroke, then tapping doesn't work.

There's a 500ms timeout (provided 2+ key presses) after the last key event. If
you put your palm down within that timeout, it'll be detected as dwt palm.
After those 500ms it'll be detected based on pressure/size/whatever. I
definitely put my palm down within those 500ms, if you run libinput
debug-events --verbose it'll print the type of palm detection triggered.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/wayland-bugs/attachments/20171107/6b659e6c/attachment.html>