All Taskbars are inflated on VirtualDisplays. We should ignore
DEFAULT_DISPLAY.
Flag: TEST_ONLY
Bug: 415326979
Test: Taskbar tests
Change-Id: If6700929840552001a8b16fa969003f2c21b3cfe
These are not being used yet in Taskbar, but they are hardcoding
DEFAULT_DISPLAY for the primary ID. In tests, we want the primary to be
considered the ID of the virtual display tests are running on.
This change also moves dagger classes to its own file for organization.
Flag: TEST_ONLY
Bug: 415326979
Test: Taskbar multivalent tests
Change-Id: Ibd0cdf46bc53dbd7a3dd5f34d7171d9a6cdebb38
* changes:
Add support for save app pairs to recents in window
Update RecentsView to allow re-apply load plan
Update AbstractQuickStepTest to check non-recents states correctly
Added logic to check if handle view alpha should be updated during SysUi
flag updates.
Fixes: 417125892
Test: Manual. Create a new bubble on the home screen, observe the stash
handle is not visible.
Have stashed bubble bar and multiple system languages.
Go to settings (or ane other apps that has input fields). Click on
search to trigger keyboard pop up. Observe that stash handle is hidden.
Collapse the keyboard and observe that stash handle is shown again.
Flag: EXEMPT bug-fix
Change-Id: I0976f37ca24ba816ee5eed6d4f1b4e6999b54c29
Added logic to preserve overview screen state on the taskbar.
Fixes: 416418164
Test: Manual. Go to overview with the bubble bar. Expand bubble bar.
Rotate device. Observe the taskbar remains stashed.
Flag: EXEMPT bug-fix
Change-Id: I197c1b7f20b23a6b2a343b18b4da0aa45beb8c52
- Instead of using enableOverviewOnConnectedDisplays from aconfig
directly, use WindowManagerProxy to use RecentsWindowFlags so that we
can use DesktopExperiencesFlags version for dev option.
Bug: 413609179
Test: m
Flag: EXEMPT flag infra
Change-Id: Iaacf068be13282017f94360acce1eea9aa1b0e84
This CL removes haptics for long presses on 3-button-nav buttons, except
when the long press triggers a user visible action.
This means that for example the haptics for long pressing the recents
button are removed, whereas haptics for long pressing the home button
remain active since that launches circle-to-search.
Bug: 408968370
Test: Manual, i.e. verified that no haptic feedback is played when
long pressing the recents button
Flag: EXEMPT bugfix
Change-Id: Icfeade8a659a8aa4882ef139696c66f410980303
Because we were closing the recents window too quickly, the final ACTION_UP was never getting received. This change also cleans up the exit flow with the correct animation. Also posting touchModeChanged in OverviewCommandHelper to better support recents window, since the recents window may not be attached to window yet
Flag: com.android.launcher3.enable_launcher_overview_in_window
Bug: 377678992
Test: TaplTestsQuickstep.testDismissOverviewWithEscKey, TaplTestsQuickstep.testDismissModalTaskAndOverviewWithEscKey, TaplTestsQuickstep.testOpenOverviewWithActionPlusTabKeys
Change-Id: I89e6c5716c0399857722114a243ed23c20a5c43d
Save app pairs does not support 3P launchers, however the way we were checking for that case was incorrect. Updated the checks to support recents in window.
Flag: com.android.launcher3.enable_launcher_overview_in_window
Bug: 377678992
Test: TaplTestsSplitscreen.testSaveAppPairMenuItemOrActionExistsOnSplitPair
Change-Id: I6c91e0ed2aa5bc16e828f71def422d5a721c1aa1
If the recents view is not attached to window when reloadIfNeeded is called, then mTaskListChangeId will be set, but applyLoadPlan will exit early without actually applying the loaded tasks. This is an issue since the recents list will remain outdated until the task stack changes. This has been causing issues in tapl tests with recents window enabled. Delaying the setting of mAppliedTaskListChangeId until the end of applyLoadPlan to fix this.
Flag: com.android.launcher3.enable_launcher_overview_in_window
Bug: 377678992
Test: TaplTestsQuickstep.testDismissLastGridRow
Change-Id: Iaa8441a74b54f86167a7963b0005c044f355d94e
- Added a workaround to listen to onNewIntent without RecentsActivity in TouchInteractionService, allowing us to clean up the recents window appropriately
- Updated LauncherInstrumentation.executeAndWaitForLauncherStop to expect a state change instead of activity stop in 3P + recents window
Flag: com.android.launcher3.enable_fallback_overview_in_window
Bug: 377678992
Test: pre/postsubmit
Change-Id: I3756e268626d778a13be1f2c68f9d3157602534e
This cl fixes conditions of when to skip the blur. While setting any new surface, we should always apply the blur.
Fix: 417131537
Fix: 416689392
Test: Go to overview from app. Go to home from app
Flag: com.android.launcher3.enable_overview_background_wallpaper_blur
Change-Id: I16ff00cf0be554eaf9aa4f48adc23b5cec4ae3da
"applyDepthAndBlur" should be directly called when Opaqueness changes. When scrim is not opaque, blur should be applied to overview background and when scrimview is fully opaque, blur should be removed and set to 0.
Fix: 416686314
Test: Go to overview (live tile) when flag is off.
Flag: com.android.launcher3.enable_overview_background_wallpaper_blur
Change-Id: Iaad158ddb2f6dc89afefcd89a569a202a712ad47
This CL avoids refreshing DisplayInfo when the display is not freeform.
As notifyConfigChange() is expensive, we want to minimize the call.
Note: enterDesktopByDefaultOnFreeformDisplay only checks the flag state
but showLockedTaskbarOnHome can check if the display is freeform in
addition to the flag state.
Flag: com.android.window.flags.enter_desktop_by_default_on_freeform_displays
Test: TaplTestsLockedTaskbar
Bug: 416253799
Change-Id: Ief298c05c8ce46ed70055139e5e817b41f6a572d
> Adding a completionSignal when preview is generated so that callers can wait on it
> Also adding support for proving an optional screen-id for preview
Bug: 400403115
Test: atest GridPreviewTest
Flag: EXEMPT refactor and unused new API
Change-Id: I569e0ab318ad101e4f6dd808f2e1cfc39ba50bda
