Loading
[CD Cursor] Remove displayId check from windowAcceptsTouchAt
With connected displays assumption that window's display Id should always match with corresponding TouchState's displayId is not true. We should rely on window's displayId to find its display. Due to this we see hover state being unexpectedly cancelled for windows incorrectly on windowInfo updates. This CL 1. Removes the explicit displayId check from windowAcceptsTouchAt 2. Uses the WindowInfo to find displayId and corresponding transform to update hovering states when we receive a windoInfo update. Bug: 397154343 Test: atest inputflinger_tests Test: manually check hover state Flag: EXEMPT bugfix Change-Id: Id414b71656775c1737c5e88371409f67ccaa229f