diff options
| author | 2022-04-18 15:20:35 +0800 | |
|---|---|---|
| committer | 2022-04-18 09:12:33 +0000 | |
| commit | 8c09ef0f2f92da4643f1b7656e0f1cc996fafe2f (patch) | |
| tree | 369f98ba73e5ebbe417b24c722ea0784bc1e5bd1 /libs/androidfw/StringPool.cpp | |
| parent | 1b43c023faccd7a301f91d35119e7be4c2210659 (diff) | |
Check target is empty before showing it in AccessibilityFloatingMenu
Root Cause: From ag/17686873, we remove the protect mechanism that
AccessibilityManagerService might not ready to retrieve information when
the phone get booted without keyguard lock, but it will still happen if
the sequence of the object created got change, just like b/184272107 in android sc-dev.
Solution: Change to check target is empty first before showing it, this
way, we can show a11y FAB both in onUserUnlocked() and
onKeyguardVisibilityChanged(false) stage without showing empty content
a11y FAB.
Bug: 192635136
Fix: 184272107
Test: atest AccessibilityFloatingMenuTest
Change-Id: Icca1c2bbae3f0bf6cad4fb28c53b5a9e6cd9b271
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions