summaryrefslogtreecommitdiff
path: root/libs/androidfw/StringPool.cpp
diff options
context:
space:
mode:
author Yohei Yukawa <yukawa@google.com> 2024-07-17 14:19:39 -0700
committer Yohei Yukawa <yukawa@google.com> 2024-07-17 14:19:39 -0700
commita9b40f792667630828ce36df79dd9affe8c9e2c8 (patch)
treed043d6e17de06135e437a88321c09a5465a32e2f /libs/androidfw/StringPool.cpp
parent1c1954f6207b3cd46f9c6525ebb996dfde563126 (diff)
Support force-stop IME package for background users
This is a follow CL to my previous CL [1], which restored a certain de-facto behavior when triggering force-stop against a package that hosts IMEs. As explained in the commit message [1], triggering force-stop against a background user's IME package has been no-op since the initial multi-user support was introduced for IMMS [2]. With my another CL [3], however, we are finally ready to propagate force-stop signal for a background user to relevant downstream code. Let's remove this inconsistency as it is really not intuitive. There is also a corresponding CTS change [4]. [1]: I261e1c60050ee20f7673425f75588269f865ba50 3bea5bcc5fd4d684d02417b2c687c6b932afd0f9 [2]: Ib23849d352db33f0747aa9d5a178f00ac726c13b 4e1ab15b305aac26ad8819fc3b2951e20985944d [3]: I0010ab8c930c5d697227ef107264dadaea398881 c3febfe5aa8c903944e49a4366c08f05902a6701 [4]: Ia19d5a578297eaf9dcd344822352feda71781bb8 Bug: 350386877 Fix: 352758479 Test: atest CtsInputMethodInstallTestCases:ForceStopTest Flag: android.view.inputmethod.concurrent_input_methods Change-Id: Ib953d7968ea3170865f82508d616ffc4e8e91d7c
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions