In connected display, when the clear all button is clicked, instead of launching home screen, this CL waits for the new desk for the display to be created and then launch to that new desk.
Bug: 417944041
Flag: com.android.window.flags.enable_multiple_desktops_backend
Flag: com.android.window.flags.enable_multiple_desktops_frontend
Test: launch an app in connected display. Go to overview and click clear all. Confirmed the new desk is launched
Test: create 2+ desks in the connected display. Go to overview. Swipe up to remove all desk one by one. Upon the last desk removal, the new desk is launched.
Test: atest NexusLauncherTests:TaplTestsOverviewDesktop
Change-Id: I3399274afd3fd4310fb4b1c1e6916b8386d81aaf
We hide the task being split during split selection, and if a config change occurs and we need to re-init the split, we will need the icon still.
Fix: 420543918
Test: Manual.
Flag: EXEMPT Bugfix
Change-Id: Ic4db47633b62b6cbf6b4e66f74912f4c806901e0
Fix: 402219336
Test: Turn on Talkback and make sure "Add new desk" is read out when
the AddDesktopButton is focused
Flag: com.android.window.flags.enable_multiple_desktops_frontend
Flag: com.android.window.flags.enable_multiple_desktops_backend
Change-Id: Ia500114d2ac73edabe935be1920af76b0e3d4242
Fixes few instances where taskbar icon layout was calculated incorrectly
for desktop-fist taskbar, assuming that taskbar gets scaled from
transient taskbar sizes to pinned taskbar (which is not the case).
Adds logic to determine whether taskbar supports transition to transient
taskbar to TaskbarFeatureEvaluator, and uses that values in place of
directly checking whether three button nav is enabled.
Bug: 413494672
Flag: com.android.window.flags.enable_desktop_taskbar_on_freeform_displays
Test: Manual - observe the taskbar layout on a desktop device.
Change-Id: Ie0d44ee5be90024ba405f652bbfd888ed22c393b
Add a border to the TaskContentsView inside a DesktopTaskView when
hovered with the mouse.
Flag: com.android.launcher3.enable_desktop_exploded_view
Test: manual
Bug: 353949686
Change-Id: I49d72266f88142b012c0fd0aa32b0b17d50eaff0
This is needed as there is no guarantee content mode will be enabled everytime sys decor flag is enabled.
Bug: 422070126
Test: NA
Flag: EXEMPT bug fix
Change-Id: I6bb85e320448448bc7ce1756250a81747f0cbb42
Also add check to SpringSet end listener to ensure it only fires once.
Fix: 420232180
Test: Manual.
Flag: com.android.launcher3.enable_expressive_dismiss_task_motion
Change-Id: I87e023c7bf019a22b5d5b91b2ee30547250c9cd1
TaskbarLauncherStateController needs to be aware of both Launcher's and recent window's statemanagers to update the taskbar state properly. Adding recents window state checks
Flag: com.android.launcher3.enable_launcher_overview_in_window
Bug: 377678992
Test: pre/post submit
Change-Id: I8b812bec3826f90d63dd710be5093deca726b11d
During transition from live tile app in overview to app, we need to
synchronise the transaction. Transaction should be applied immediately
only when live tile becomes static tile.
Fix: 420918073
Test: Tap on live tile to launch.
Flag: com.android.launcher3.enable_overview_background_wallpaper_blur
Change-Id: I6e0e333d0fe8417e8c8f5d87e5f80fa9b11fdad4
Problem: upon exiting the deesktop mode we were getting change in recents tasks which we were commiting to ui and that resulted in hotseat flashing.
Solution: since layout transition is only in use while we are in desktop windowing mode, we will only need to change icon layout bound while we are in desktop mode and not when we are exiting.
Test: Manual, Presubmit
Bug: 417696108
Bug: 415700104
Flag: EXEMPT bugfix
Change-Id: Ibcf65df49e7b48312a27d2750d3d0c6c5d392006
spring into place from 40 dp offscreen:
expressive default spatial spring
damping: 0.8,
stiffness: 380
Bug: 399642211
Flag: com.android.window.flags.enable_multiple_desktops_frontend
Flag: com.android.window.flags.enable_multiple_desktops_backend
Test: create desktop and check animation
Change-Id: Ie15b4f58d394590ea24d72036a587111f1e6cf3b
Problem:
The framework prevents a key gesture handler from being re-registered by the same process ID. In `TaskbarAutohideSuspendControllerTest`, we observed two calls to `QuickstepKeyGestureEventsManager#registerAllAppsKeyGestureEvent`. The first call originated from TouchInteractionService (as expected). The second, however, came from a new TaskbarManager instance created within `TaskbarbarUnitTestRule`. This occurs because `TaskManager#recreateTaskbarForDisplay` triggers `AllAppsActionManager#isTaskbarPresent`, which ultimately leads to the duplicate call to `QuickstepKeyGestureEventsManager#registerAllAppsKeyGestureEvent`.
Solution:
Since this problem only occurs in tests and not in practice, we can mock out `QuickstepKeyGestureEventsManager`'s [un]registration calls to do nothing within `TaskbarbarUnitTestRule` to prevent duplicated re-registration.
Flag: com.android.window.flags.grant_manage_key_gestures_to_recents
Test: atest NexusLauncherTests:TaskbarAutohideSuspendControllerTest
Test: atest NexusLauncherTests:TaskbarEduTooltipControllerTest
Fix: 421853013
Change-Id: Ic87bd8d36ce018935002b8698b1d53e30b2fca6d