The OtherActivityInputConsumer inverted log was inadvertently
added in ag/28270874.
Flag: EXEMPT logs only
Bug: NA
Test: Manual
Change-Id: Iab5de4ec26bd40d18bdcdea62ec7ecb685fec6a1
This CL updates a test to verify the behaviour while swiping up from a fullscreen app to Overview and checking if that TaskView is between DesktopTasks (right side) and Grid Tasks (left side).
The test adds the following validations:
- Launches adjacent task while DesktopTask is at the center of the screen
- Swipe up from a fullscreen app to Overview to validate whether the task is between other tasks and desktop tasks.
- Fling back to DesktopTask to dismiss the adjacent focused task
Fix: 353948167
Flag: com.android.launcher3.enable_large_desktop_windowing_tile
Test: TaplTestsOverviewDesktop
Change-Id: Iaa15d4061c3b6ba8fc0d03416b4721cdf3f047c3
The expected order to finish recents is first "setWillFinishToHome"
and then "finish" via RecentsAnimationControllerCompat.
Because RecentsAnimationController uses UI_HELPER_EXECUTOR to invoke
setWillFinishToHome, if "finish" is called on UI thread directly,
there may be a race that WillFinishToHome is not set yet (only when
animation is disabled), then the shell's RecentsTransitionHandler
will handle it as "return to app" rather than entering recents.
By using the regular finishRunningRecentsAnimation (forceFinish is
false), RecentsAnimationController#finishController will also post
to UI_HELPER_EXECUTOR, so the order between setWillFinishToHome can
be consistent.
Bug: 375667878
Flag: EXEMPT bugfix
Test: atest com.android.quickstep.FallbackRecentsTest#testOverview
Test: Set 3rd party home as default.
Disable animation (Settings's "Remove animations").
Press recents key on home. It should enter recents.
Change-Id: Ia449f77b317db812360092c2aaf9e3657b92cf7b
This CL does not include animating app icons / leave behind circle.
Bug: 376281549
Flag: com.android.launcher3.taskbar_overflow
Test: press the oveflow button, dismiss KQS in different ways
Change-Id: I1f830c6859a5be4fb5947ec38e6d30da79138b7f
Refactor the TaskbarDelegate to support multiple pass down displayId specific signals down to the taskbar level.
Flag: EXEMPT not adding new behavior
Bug: 376128251
Test: Manual
Change-Id: I61aef4eb746d671be69eefeb15d876d48dd9a8fa
The implementation in this CL is no-op i.e. all widgets will be shown
Bug: 356127021
Flag: com.android.launcher3.enable_tiered_widgets_by_default_in_picker
Test: Verified with other child cls
Change-Id: I0a6f8973dc8ec58fd87d29b3f291b5e290ea988d
When the second app is selected, check if there is a background task
that matches the intent provided and start the task if there
is one.
This is done to correct an issue where freeform background tasks opened
via intent will open in the correct split stage but in freeform
windowing mode and bounds.
Bug: 338382550
Test: manual
Flag: EXEMPT bugfix
Change-Id: Ibefe4b5045cbcefdbc71c99c4eaba4fdf67d7a0e
This change ensures that we're updating the distance to the flyout's
collapsed position before we start collapsing it. The distance is
initially calculated before we start expanding, but when a new bubble
is added while we're fully expanded, and if we previously had 1
bubble and now have 2, the collapsed position changed, so we need to
update it before we start collapsing.
Flag: com.android.wm.shell.enable_bubble_bar
Bug: 376276297
Test: manual
- dismiss all bubbles
- create 1 bubble
- after the flyout is fully expanded create a second bubble
- observe the flyout is updated with the contents of the second
bubble
- observe when the flyout collapses, it collapses to the dot
on the second bubble
Change-Id: I219886fd6463d69692d9945d901d1f3ad3cb26a0