diff options
| author | 2025-03-21 11:19:39 +0000 | |
|---|---|---|
| committer | 2025-03-24 09:21:09 +0000 | |
| commit | 473cd952fd34fdf7dab2c66c0db917f4866fd7ed (patch) | |
| tree | f96cc8002aab79a72db86616cb0c1f0ca081ce32 /libs/androidfw/FileStream.cpp | |
| parent | 3d4dbbea8327a82f8a2f5b9e50c6083cf6f80bbe (diff) | |
Force report resizing after window token is reparented
Without this, VRI was updating back the context display id to the previous one before receiving the onDisplayMoved callback (that was sent one frame later).
This caused one configuration change to be received with correct resources and configuration, but while the windowContext had wrong display ID.
During the configuration change, some SysUI classes were also using the context display id to have different layouts, and they were broken.
With this, the VRI receives the new resize callback earlier, and we never update the context display id from VRI to the old one.
The API is essentially only called when com.android.systemui.shade_window_goes_around flag is enabled.
Bug: 362719719
Bug: 388886443
Bug: 403570017
Bug: 405216230
Test: from shade collapsed, expand in a different display. Observe only one config change happens, and the context doesn't change display id more than once.
Flag: com.android.window.flags.reparent_window_token_api
Flag: com.android.systemui.shade_window_goes_around
Change-Id: Id6e1b872daa6f7b00b833644b82438d436cf04d9
Diffstat (limited to 'libs/androidfw/FileStream.cpp')
0 files changed, 0 insertions, 0 deletions