b37f32cfeceb76dd8ae9976575191a5620877dab
This CL fixes a regression that
InputConnection#reportFullscreenMode()
is always called back on the main thread rather than its associated
thread. In most of cases those two threads are the same hence there
is no semantic problem, threads are the same, but for some special
cases, e.g. when apps explicitly override
InputConnection#getHandler(),
our thread affinity contract can be violated.
This regression was accidentally introduced in Android O time frame
while attempting to make the system more robust at Bug 28406127 [1].
Although we have never received any actual issue report from app
developers so far, this is still worth fixing.
[1]: If23e7c7c265ab3dfb48c2fb6fdb361b17d22c594
2bc66171cc
Bug: 28406127
Fix: 193588937
Test: atest CtsInputMethodTestCases:InputConnectionHandlerTest
Change-Id: Id3ac21c11d6b062bb66719109376ff642309b8ff
…
…
Merge "Remove system-headers, minimize unwanted warnings." am:
4e6598eef7 am: 6c423b166c am: df6f18e77a am: 6bf41e2475
…
…
…
…
…
…
…
…
…
…
…
Merge "Disable unlocked screen off if the display needs blanking." into sc-dev am:
15e77132cc am: e1a8cbf1ba
…
…
…
…
Merge "Fix testRelaunchConfigurationChangedWhileBecomingVisible flakiness" into sc-v2-dev am:
bebfe77990 am: 4859b30a59
…
…
…
…
…
…
Description
No description provided
Languages
Java
73.7%
Kotlin
14%
PowerBuilder
5.8%
C++
5.2%
AIDL
1%