summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Cosmin Băieș <cosminbaies@google.com> 2024-03-14 11:40:32 +0100
committer Cosmin Băieș <cosminbaies@google.com> 2024-03-14 11:40:32 +0100
commitb4b74c5201ee5a62ab3c7f5f695a0a5491de5b71 (patch)
tree0ef9a0e07ec13baf1440c91fafbd1831f7db86bb /libs/androidfw/StringPool.cpp
parentcaa556be3233cf62484577f04e19bcda0614a5d1 (diff)
Wait for leash in ImeInsetsSourceConsumer
Currently if we have an IME show request before the client has the InsetsSourceControl, we mark this in mIsRequestedVisibleAwaitingControl and re-try to show when we gain the control. However, if we gain a control without a leash, we reset this awaiting control flag, but we still cannot show. When we eventually get the control with the leash later on, the awaiting control flag is reset, so we don't actually re-try to show, when we should and could do so. This takes into account both the availability of the control, and the leash on the control, set in mIsRequestedVisibleAwaitingLeash. These should fix any timing issues due to code changes such as [1]. [1]: Ie7bb268f228ae8a8ed15e49b193aa2d0183f31ac Bug: 328374719 Test: atest ImeInsetsSourceConsumerTest#testImeRequestedVisibleAwaitingControl ImeInsetsSourceConsumerTest#testImeRequestedVisibleAwaitingLeash WindowInsetsControllerTests#testShowImeOnCreate WindowInsetsControllerTests#testShowImeOnCreate_doesntCauseImeToReappearWhenDialogIsShown Change-Id: I2fb3bf1dc057f85a9f8ad0166ec25519aa004905
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions