4773ee18a204bac6ae724875a7e6c54ab626ba59 - platform/frameworks/base

commit	4773ee18a204bac6ae724875a7e6c54ab626ba59	[log] [tgz]
author	Yohei Yukawa <yukawa@google.com>	Mon Dec 24 21:13:53 2018 -0800
committer	Yohei Yukawa <yukawa@google.com>	Mon Dec 24 21:13:53 2018 -0800
tree	a54e1077ff5492c7bb8fa5cd49675171c3b328bf
parent	2232e861862566418da649290d86f7d2734fffb7 [diff]

Stop supporting null IME token in IMM#setInputMethodAndSubtype()

Hopefully no one has relied on this undocumented behavior that when
the caller has WRITE_SECURE_SETTINGS then null IME token is allowed in
IMM#setInputMethodAndSubtype().

Note that if the caller had WRITE_SECURE_SETTINGS they can achieve the
same goal by directly updating the following secure settings:
  * Settings.Secure.DEFAULT_INPUT_METHOD
  * Settings.Secure.SELECTED_INPUT_METHOD_SUBTYPE

Bug: 114488811
Test: CtsInputMethodServiceHostTestCases
Change-Id: Ic5c59299ace16778fc57a4ec2639508564f416a7

core/java/android/view/inputmethod/InputMethodManager.java[diff]
core/java/com/android/internal/view/IInputMethodManager.aidl[diff]
services/core/java/com/android/server/inputmethod/InputMethodManagerService.java[diff]
services/core/java/com/android/server/inputmethod/MultiClientInputMethodManagerService.java[diff]

4 files changed

tree: a54e1077ff5492c7bb8fa5cd49675171c3b328bf