diff options
| author | 2024-03-07 06:28:59 +0000 | |
|---|---|---|
| committer | 2024-03-21 07:30:03 +0000 | |
| commit | f75ad18ed082dd0a95ab277f8214b1070e1fc8d6 (patch) | |
| tree | 30957518014efbcf5015bd36a8ae5874f0f6a977 /libs/androidfw/StringPool.cpp | |
| parent | 99075875adc670ea7a3ef409ddc85d41f7095c07 (diff) | |
fix(magnification): directly use the window touchableRegion in AccessibilityController magnification recomputeBounds
In AccessibilityController recomputeBounds, currently it create a touchable rect from the WindowState's touchableRegion to compute the magnification region. However, if there are separated rects in the touchableRegion, then the created touchable rect might be a large rect consisting of non-touchable areas in that WindowState. Therefore, the fix is to directly use the WindowState's exact touchableRegion in computation so the non-touchable areas will not be included. The fix is guarded behind a flag to verify with rollout process, so we can check if there are some side-effect or performance issues.
Bug: 323366243
Flag: ACONFIG com.android.window.flags.use_window_original_touchable_region_when_magnification_recompute_bounds DEVELOPMENT
Test: manually flip flag
atest AccessibilityMagnificationTest
Change-Id: I4681e286f7b4465fca5c77d579be104ff73ad42f
Diffstat (limited to 'libs/androidfw/StringPool.cpp')
0 files changed, 0 insertions, 0 deletions