summaryrefslogtreecommitdiff
path: root/core/java/android/inputmethodservice/InputMethodService.java
diff options
context:
space:
mode:
authorMing-Shin Lu <lumark@google.com>2022-01-24 16:04:28 +0800
committerMing-Shin Lu <lumark@google.com>2022-01-24 16:18:00 +0000
commit9600d66d6d89b6fb305b8384e752aefc4957b761 (patch)
treed5ccde2bd478ba71b417789e85337575581aa3ca /core/java/android/inputmethodservice/InputMethodService.java
parentda433c60c1be2ab162078929fe0958de7c4d967e (diff)
Fix testGetSettingsContextOnDualDisplayContent flakiness
The test is to verify the window configuration of the IME menu context (made by createWindowContext from SystemUiContext) is same as the IME containter's bounds that placed on the given display area, In case WindowTokenClient#onConfigurationChanged may come after the server side's configuration change (Since it's the async call), before calling assertImeSwitchContextMetricsValidity, we have to verify both server and client side has received the onConfigurationChanged callback to prevent the test flakiness. Fix: 215874086 Test: atest InputMethodMenuControllerTest#\ testGetSettingsContextOnDualDisplayContent --rerun-until-failure 20 Change-Id: Ia915362ff6d81cfb1eb39f426cbf41355c12fa05
Diffstat (limited to 'core/java/android/inputmethodservice/InputMethodService.java')
0 files changed, 0 insertions, 0 deletions