tree f9753dd4699d02b45c206e5d2e41115645eb9960
parent 838d875bfea097d8d6ea9ac22460526b39fbc644
author Dave Mankoff <mankoff@google.com> 1617726513 -0400
committer Dave Mankoff <mankoff@google.com> 1617734430 -0400

Ensure that FalsingManager#isFalseTap handles delayed clicks.

Views, be default, don't immediately process touch events as clicks.
Instead, they post an internal runnable to the main thread that then
runs the click. This was tripping up the FalsingManager, as a recent
change meant that it no longer saw the motion events.

With this change, the FalsingManager will look at prior events if
the recent events are empty.

Fixes: 184635871
Test: manual
Change-Id: I69981b09837d8a1d94b3a033243bce7a2d31844c