Add default spring methods for running dismiss on a task.
Fix: 404206966
Test: Manual.
Flag: com.android.launcher3.enable_expressive_dismiss_task_motion
Change-Id: Ic7c5b82d6b504a31193ba85b0c79dd89be344c22
Revert submission 32704934-model-test-cleanup
Reason for revert: Droidmonitor created revert due to b/406588406. Will be verifying through ABTD before submission.
Reverted changes: /q/submissionid:32704934-model-test-cleanup
Change-Id: Ieeb7f5b5699afeae27f946f060147bb68afc36e5
> Using Sandbox application everywhere to avoid test leaks
> Removing LauncherModelHelper and moving some utility methods to rules and extensions
Bug: 406521480
Flag: EXEMPT test only
Test: Presubmit
Change-Id: I17bd5ec2bdb0fc0cbe02be9c8ee76595effe3f11
Previously was still relying on spring driver to end, even if driving no neighbors.
Update live tile before canceling animation to bring task off screen, or else it may still show at the top of the screen.
Fix: 405364868
Test: Manual
Flag: com.android.launcher3.enable_expressive_dismiss_task_motion
Change-Id: Ic9a1b4ba9aaf1ec3830e49bf15573388a6d7a2ad
This CL will fix the issue when the app chip is bigger than the TaskView and doesn't respect its maxWidth value.
Also fixes the bug when the first chip expands when taps over the second app chip.
Fix: 406225230
Flag: com.android.launcher3.enable_overview_icon_menu
Test: OverviewImageTest
Test: OverviewSplitTaskImageTest
Change-Id: Id1c806a320522e6d5bda3d4d8712a43637c57834
- Move the logic to query for focused displayId from
OverviewCommandHelper to TouchInteractionService.
- This way the OverviewCommandHelper code always uses command.displayId
in its code.
Bug: 404757863
Test: manual run CUJ
Flag: com.android.launcher3.enable_alt_tab_kqs_on_connected_displays
Change-Id: Ia9b05e64b549895f029bc5204169cf84474af125
- With com.android.window.flags.enable_task_stack_observer_in_shell
enabled, the correct task visibilty is reported to TTT, which in
combination with the incomplete TaskStackListener signals results
in tasks being reported as visible when they shouldn't be. This is
most apparent when the top task is excluded from recents, which
results in us attempting to pull the next visible non-excluded task
to show as the current running task (resulting in the live tile/
thumbnail being shown on the wrong task).
Instead, we're expanding the workaround behavior to also check for
any fullscreen task that fills its parent (ie. is not transparent)
and using that as a signal to reset the visiblity of tasks behind it.
Bug: 390564114
Flag: EXEMPT bugfix
Test: Manual, expand PIP above another task and ensure that the other
task's visibility (as reporting in TTT) is invisible if the
expanded PIP task occludes it
Change-Id: Ieaa5460c2671d91f30b75aaf5317ab5ddb42315b
The flag will be applied at the code using this use case.
Bug: 405974619
Fix: 405974619
Flag: com.android.launcher3.enable_refactor_digital_wellbeing_toast
Test: GetRemainingAppTimerDurationUseCaseTest
Change-Id: I939b3447b93e7e84eb69032aa0f67c1629f916c1
The usage of this chain will be flagged
Bug: 405359454
Fix: 405359454
Flag: com.android.launcher3.enable_refactor_digital_wellbeing_toast
Test: AppTimersRepositoryTest
Change-Id: Ife0db79175dd30982a0cb179369a3cea470ef7ba