summaryrefslogtreecommitdiff
path: root/core/java/android/inputmethodservice/AbstractInputMethodService.java
diff options
context:
space:
mode:
authorJacky Kao <jackykao@google.com>2021-11-30 10:14:28 +0800
committerJacky Kao <jackykao@google.com>2022-01-10 14:39:32 +0800
commit3b328cce652bf84d1a94c66f9f4eef897fcd5617 (patch)
tree2250164150fe0f8773998b998e83e3314d2dfe17 /core/java/android/inputmethodservice/AbstractInputMethodService.java
parent96ceaf62e492cf71b3bf74faa0f3d502b66c3f9b (diff)
Apply display transform to window bounds and node bounds
Currently, the node bounds and the window bounds are both in unrotated coordinates, it means if their layout is not changed, then the bound wouldn't be change after rotating the device. This effects Uiobject2, which is used for uiautomator, because it clips the nodes bounds based on current display metrics. see ag/13805539. To fix it, we transfer them back to the rotated coordinates based on the displayInfo called back from the surface flinger. (Co-Author: Ryan) Bug: 191736824 Test: a11y CTS & unit tests Test: atest NexusLauncherTests & Launcher3Tests Change-Id: I14c5e98895c370abe11b08c466bb7091f7ea613e
Diffstat (limited to 'core/java/android/inputmethodservice/AbstractInputMethodService.java')
0 files changed, 0 insertions, 0 deletions