diff options
| author | 2025-02-18 14:42:15 -0800 | |
|---|---|---|
| committer | 2025-02-18 14:42:15 -0800 | |
| commit | c22e3d2ff9aa8bc3d526b2c652ca46d5c94b364e (patch) | |
| tree | 0336ae7736148d5ae8d0324593445aed4f6543b0 | |
| parent | 34b8ee40f667f25d2012bbe2b0d5a5e9f45a34ee (diff) | |
Fix local coordinates for touchable region
The region and mGivenTouchableRegion are in frame-local coordinates, so
the mTmpRegion here should be in local coordinates too. As has been
pointed out in the issue tracker, the intent here was to get the frame
size in its own coordinates instead of absolute right and bottom
coordinates.
Change-Id: I7d3256134d7e447bbd3d4e6edc937d38fe5f0ac7
Test: Not added
Flag: EXEMPT bugfix
Bug: 358274057
| -rw-r--r-- | services/core/java/com/android/server/wm/WindowState.java | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/services/core/java/com/android/server/wm/WindowState.java b/services/core/java/com/android/server/wm/WindowState.java index 9f1289b2c12a..23cf44533a25 100644 --- a/services/core/java/com/android/server/wm/WindowState.java +++ b/services/core/java/com/android/server/wm/WindowState.java @@ -2652,7 +2652,7 @@ class WindowState extends WindowContainer<WindowState> implements WindowManagerP // The client gave us a touchable region and so first // we calculate the untouchable region, then punch that out of our // expanded modal region. - mTmpRegion.set(0, 0, frame.right, frame.bottom); + mTmpRegion.set(0, 0, frame.width(), frame.height()); mTmpRegion.op(mGivenTouchableRegion, Region.Op.DIFFERENCE); region.op(mTmpRegion, Region.Op.DIFFERENCE); } |