summaryrefslogtreecommitdiff
path: root/media/tests
diff options
context:
space:
mode:
author Liran Binyamin <liranb@google.com> 2025-01-09 11:44:04 -0500
committer Liran Binyamin <liranb@google.com> 2025-01-09 15:38:08 -0500
commita42b25dad65bb65599222930d7123beac1622bd4 (patch)
tree9adb32e1345714b51af675b9d1f1f918952e7cc0 /media/tests
parentd368357c39bd85932a2faf8e2bb42e1a7c714469 (diff)
Update imeTop calculation in DisplayImeController
The calculation of the imeTop value that's used in the callbacks of DisplayImeController.ImePositionProcessor is offset by the top inset of the surface. This change updates the calculation so that the value sent to consummers is in screen coordinates. The only consummers of the API at this moment are Split and Bubbles, neither of which uses the value directly to position views. Bubbles uses the values to calculate the IME height, and Split does IME height calculation as well as determining the progress of the animation. But the expression uses values that are equally offset, so the offset gets canceled out. This makes this change effectively a no-op. Bug: 377329425 Flag: EXEMPT bugfix Test: manual: - have 2 apps in vertical split (use an app with an input field at the bottom for the bottom split app, e.g. bubbles test app) - request IME in the bottom app - observe IME and split animations Test: manual: - repeat test above with horizontal split Test: manual: - have a floating bubble - move stack to bottom of the screen - launch app and request IME - observe stack animates above the IME - hide IME - observe stack animates back to its previous position - expand bubble and request IME - observe expanded view animates correctly Change-Id: I6e90fd140bc9577a9c10ffe76819b90330726601
Diffstat (limited to 'media/tests')
0 files changed, 0 insertions, 0 deletions