tree c889f79183bc8c66ae60c1b7fd7e087a6595ea20
parent 74c2df55117e7e3f23aaf906fa7edce2dcb9f8dd
author Bernardo Rufino <brufino@google.com> 1610989137 +0000
committer Bernardo Rufino <brufino@google.com> 1610992058 +0000

Don't block touches if same application token

Don't block touches from windows if they have the same application token
as the touch-consuming window.

That is only set for activities and could be shared by sharing the
activity's LayoutParams with another app. This is how AGSA/Launcher's
integration (-1 screen and search pill) is done (check
http://b/166617888#comment5).

This fixes the bug where touches were being blocked in the AGSA/Launcher
-1 screen animation. Note that we fixed the final state before
(b/166617888) via alpha = 0 exemption, now we are also fixing the
animated state where alpha != 0.

Also remove redundant ownerUid check since that was incorporated in
canBeObscuredBy() (ag/12714766).

Bug: 166617888
Bug: 158002302
Test: Trigger -1 screen <> launcher animation, tap the screen while
      animating and verify no touches blocked.
Test: atest WindowUntrustedTouchTest WindowInputTests inputflinger_tests
      inputflinger_benchmarks libinput_tests libgui_test
Test: CTS coming
Change-Id: I8e016917b1981d99a5550708f3ec27781e03f988