diff options
| author |   lumark <lumark@google.com> | 2019-05-31 17:13:13 +0800 |
|---|---|---|
| committer | Ming-Shin Lu <lumark@google.com> | 2019-09-11 02:02:48 +0000 |
| commit | 87f14f1e18776919bd6d094943544d1982a421f7 (patch) | |
| tree | 3b1b9217cf9d5c3a32a0a3c830ea3f88c15fe73c /java/src/com/android/inputmethod/accessibility/KeyboardAccessibilityDelegate.java | |
| parent | ccb19fdda7a4ef49eeb6195b6a43ffedb269c670 (diff) | |
| download | latinime-87f14f1e18776919bd6d094943544d1982a421f7.tar.gz latinime-87f14f1e18776919bd6d094943544d1982a421f7.tar.xz latinime-87f14f1e18776919bd6d094943544d1982a421f7.zip | |
Create display context when switching IME to new display for AOSP IME
To address IME service context's Resources / DisplayMetrics update
when switching IME window to another display after onConfigurationChange.
We use Context#createDisplayContext to create display specific context when
display changed, to ensure soft keyboard can re-layout with correct resources.
Bug: 126930163
Test: manual with AOSP IME as below steps:
1) Settings > Developer options > enable "Simulated Display" & "Force desktop mode".
2) Reboot device
3) Launch app (i.e. Contacts) with bluetooth or usb mouse in Simulated display.
4) Tap EditText on app to see see if IME window layout correctly on simulated display.
5) Launch app (i.e Files) on primary display.
6) Tap EditText on app to see if IME window layout correctly on primary display.
Change-Id: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
Merged-In: I0ed6a079af1ed90c75fee1d36d5ce3ef3c41f8ed
Diffstat (limited to 'java/src/com/android/inputmethod/accessibility/KeyboardAccessibilityDelegate.java')
0 files changed, 0 insertions, 0 deletions