tree 10fe025413b7c56ac57126d580db2e37f5045945
parent 36f5994c6392fd1b17816fd52fef0a61f5cb9b52
author Prabir Pradhan <prabirmsp@google.com> 1695290033 +0000
committer Prabir Pradhan <prabirmsp@google.com> 1696533282 +0000

InputDispatcher: Use correct coordinate space when canceling motions

Input targets for synthesized cancellations were not created using the
same pipeline as normal dispatching. Due to this, things like window and
display transforms were not being applied to the events. This means
ACTION_CANCEL events did not have the correct coordinates in many cases.

Here, we fix that by attempting to use the same pipeline as normal
dispatching for creating the input target. When it's not possible to do
due to there being no window (e.g. for global monitors), we fall back to
creating the target ourselves.

Bug: 287908447
Test: atest inputflinger_tests
Change-Id: Ic82f87c55e4eaf3e87b07986a14933fbdb69e042