summaryrefslogtreecommitdiff
path: root/api/api.go
diff options
context:
space:
mode:
author Ats Jenk <atsjenk@google.com> 2024-12-19 11:51:44 -0800
committer Ats Jenk <atsjenk@google.com> 2024-12-19 16:02:05 -0800
commit3845228cbdb362b91fd91b635a7f6a3808b992b7 (patch)
tree532002673a696d554e297f6c5358d042c814ad74 /api/api.go
parent54b6d1a340bc39166a1e8927ad4171101074e2e1 (diff)
Check that there is an existing expanded view to switch from
When switching between bubbles, we use the switch animation. Switch animation expects there to be 2 expanded views: from and to. If one of these is null, the animation is skipped. In case of removing a bubble, we do have the previous bubble, but the expanded view is removed. Since the bubble is still there, we still try to perform the switch animation. Which fails. When the switch animation fails, we do not remove the previous bubble views for the container and leave it on screen. The task view itself is removed and this leaves only the handle in the container. Which causes a shadow to remain on screen. Ensure that there is an expanded view to switch from before attempting the switch animation. If there is not, fall back to the expand animation. This also ensures that the previous bubble container is immediately removed. Bug: 384059425 Bug: 383613997 Test: have multiple bubbles, dismiss the expanded bubble by: - dragging to dismiss target - dismiss it from the app handle menu - set it to not bubble from the app handle menu check that in all instances the bubble is removed and there is no shadow on screen, and that a new bubble is opened Test: atest WMShellMultivalentTestsOnDevice:com.android.wm.shell.bubbles.bar.BubbleBarLayerViewTest Test: atest WMShellRobolectricTests:com.android.wm.shell.bubbles.bar.BubbleBarLayerViewTest Flag: com.android.wm.shell.enable_bubble_bar Change-Id: I649ed31df9e5ab5796bf80e6fff1b8aab7e98299
Diffstat (limited to 'api/api.go')
0 files changed, 0 insertions, 0 deletions