diff options
| author | 2024-07-25 10:43:42 -0700 | |
|---|---|---|
| committer | 2024-07-25 10:43:42 -0700 | |
| commit | a5ebd6b7812136ab2d98f0ac0b8fa6aed2862193 (patch) | |
| tree | abb62ca8d547751298d6e60f9ebf428689b34cd5 /libs/androidfw/StringPool.cpp | |
| parent | 755a500ccc2394a6a59ad24329261f36b51851dd (diff) | |
Remove ZeroJankProxy.Callback#isInputShownLocked()
This reworks our previous CL [1], which addressed an observable
unintentional behavior change when ZeroJankProxy is enabled, in a way
that ZeroJankProxy.Callback does not need to have
ZeroJankProxy.Callback#isInputShownLocked(),
which will soon need to become concurrent multi-user aware.
The problem is when it becomes concurrent multi-user aware,
ZeroJankProxy needs to know whose IME is in use, which is tricky
because the IME user ID is dynamically resolved with
InputMethodManagerService#resolveImeUserIdLocked().
The core logic should remain unchanged.
[1]: Ie2f262128eb32db5a7922373fdfaebd2945ea36a
2aed68440258fbc3cdb803d4faa1855638579bf1
Bug: 349904272
Test: presubmit
Flag: android.view.inputmethod.use_zero_jank_proxy
Change-Id: Ib719f6018965c3554c8c2d8c2050ad51962d8a25
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions