diff options
| author | 2024-12-20 11:48:22 -0800 | |
|---|---|---|
| committer | 2024-12-20 23:49:04 +0000 | |
| commit | 82dbc03e5efca46de5817cebbaa25401a4e539fb (patch) | |
| tree | 2ebc1b6e3ab66de7d40c0bc4d5c5e70ddc0a2ad7 /libs/androidfw/StringPool.cpp | |
| parent | 0a30919eff26db657287e9c37bacde3a02b466d0 (diff) | |
Introduce feature flag for fallback display for secondary user on secondary display
The IME fallback mechanism is used when the soft input keyboard is expected to appear on a display separate from the one showing the app that is consuming the key input events.
For example, if an app runs on a virtual display created with the DISPLAY_IME_POLICY_FALLBACK_DISPLAY policy, its soft input keyboard will be shown on a designated fallback display, which is currently hardcoded as the DEFAULT_DISPLAY. But that doesn’t work with visible background users. Visible background users have a secondary display other than DEFAULT_DISPLAY as their main display.
Running CtsWindowManagerDeviceIme:MultiDisplayImeTests#testCrossDisplayBasicImeOperations for visible background user is the easier way to reproduce this bug.
Command line to run testCrossDisplayBasicImeOperations for visible background user:
```
atest --user-type secondary_user_on_secondary_display CtsWindowManagerDeviceIme:MultiDisplayImeTests#testCrossDisplayBasicImeOperations
```
Bug: 383228193
Test: m
Flag: android.view.inputmethod.fallback_display_for_secondary_user_on_secondary_display
Change-Id: I283cd17ce962de5d9c1975d98921f60d7eeb203b
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions