diff options
| author | 2024-09-26 17:00:32 -0700 | |
|---|---|---|
| committer | 2024-10-02 23:21:44 +0000 | |
| commit | 9968e51d0f6f3781e0d4ca266e675b5e532a5628 (patch) | |
| tree | a15146357cff4151ba66023d45a141dc5b967277 /api/api.go | |
| parent | fba7eececa67f6fc4d9e49b154ffba931acfb642 (diff) | |
Fix top and bottom swipes not working after touches on glanceable hub
The bouncer and shade touch handlers coordinate carefully with the
hub's touch handling to allow for vertical swipes on the grid itself,
as long the hub iself is not consuming the touch. The hub relied on the
touch handlers to reset the nested scrolling state between touches.
However, if the touch is entirely consumed by the hub, such as when
tapping on a CTA tile button, scrolling on a widget has a list, or
moving the UMO, the touch state is not reset. This leads to gestures
that are not nested scrolls, such as swiping up from the very bottom
for bouncer or very top for shade to not work.
This CL resets the touch scroll state when a touch consumed by the hub
ends to fix these issues.
Bug: 368420327
Fixed: 368420327
Flag: com.android.systemui.communal_hub
Test: manually verified on device
(cherry picked from https://googleplex-android-review.googlesource.com/q/commit:20b553d64084aa36703ee4b2f922debd4fc591a9)
Merged-In: Ide4e6812b7e60e5301f4e3c2d668fb337ffce86c
Change-Id: Ide4e6812b7e60e5301f4e3c2d668fb337ffce86c
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions