tree 9a99edffc19f557c809b74f3bcee59222d278af3
parent d66451ca97d9c2c4e140577fe7f11c9bfd0bc91e
author Chun-Ku Lin <chunkulin@google.com> 1679960814 +0000
committer Chun-Ku Lin <chunkulin@google.com> 1680131645 +0000

Allow Accessibility CTS to hover on the button within the touch delegate's bound, hover outside of the button on low pixel density devices.

**Root cause**
The cts is simulating hover on the views in the described sequence on the same y axis: the view with touch delegate (A - hoverLeft) > parent view (B - hoverMiddle) > sibling view (C - hoverRight) > parent view (B - hoverMiddle) > the view with touch delegate (A - hoverLeft).

It has an assumption that the hoverMiddle will be on the parent view. However, if the calculation of the position for hoverLeft, hoverMiddle, hoverRight is different depending on the device's screen density, it's easy to break the test assumption.

Changing the test position calculation to be screen density agnostic would make the test's assumption hold regardless of the device's screen density.


Bug: 275003512
Test: atest AccessibilityEndToEndTest

Change-Id: I7f9f55350a7c70ea482ff386d1eb93f66ed2c895