testOverviewForTablet was ignored for over a year and other tests cover
most of the test cases of the original test so removing
Add separate tests for grid re-balancing
Fix: 315376057
Flag: EXEMPT. Test
Test: TaplTestsQuickstep
Change-Id: I33016ccdb68b1c2039c626a6d32821de71509506
This requires a decent sized refactor. Namely, rather than relying on
mCurrentPosition we need to rely more upon mLastPosition and
mFinalPosition for increasing and decreasing dot size. We also need to
delay the animation start if we are mega-moving to have the desired
delayed dot change effect.
Bug: 407711750
Test: Verified this works locally. Please see the bug for a screenrecording that shows this correct behavior working.
Flag: com.android.launcher3.enable_launcher_visual_refresh
Change-Id: I83ef113c17f2197e3c02e85f44cf3f05947d2adb
Keep these file in synch with the nudge proto definition in //depot/google3/java/com/google/android/desktop/growth/proto.
Bug: 416054612
Test: EXEMPT add in the follow up CL
Flag: EXEMPT add separately
Change-Id: I5fe6ae7b3cb285bd1c07fd4ff54b273799ec0d98
- Use supplied TaskbarActivityContext to evaluate padding in dp instead
of Resources.getSystem that doesn't seem to provide accurate
measurement when launcher is initialising.
Fix: 414343355
Test: m
Flag: EXEMPT minor refactor
Change-Id: Ia64a7280ba60534fc949269c5886e9b32a917e03
In TaskViewUtils, the StateManager#movetoRestState method is invoked after the recents animation finishes and before the launcher state is reapplied. The issue leading to a phantom transition is that moveToRestState initiates an animation due to RecentsWindowManager#shouldAnimateStateChange always returns true.
Connected display overview is similar to 3P recents. And thus, we follow RecentsActivity#shouldAnimateStateChange to always return false.
Test: manually click on a overview tile in the connected display. No phantom animation is observed after switching to the app.
Flag: com.android.launcher3.enable_overview_on_connected_displays
Bug: 415245440
Change-Id: I3c9600cae6ce9058749365734f433f5e3cdb9445
When the home screen is shown behind desktop mode, pressing the overview button to start a transition should still animate tasks shown on top of home screen. To ensure that freeform tasks are animated, the home screen should not be considered visible when performing transitions in this case. Therefore, make getVisibleLauncher() return null, so that switchToRecentsIfVisible() doesn't animate launcher to overview without animating the freeform tasks at the same time.
Bug: 375644149
Flag: com.android.window.flags.show_home_behind_desktop
Test: Open a window, press overview button. With no windows open, press
overview button.
Change-Id: I9b1d72e35071c5b446b98a8e6c6695ff5c666222
- This is required to show a half width all apps sheet on external
monitor connected to the phone. Without this the apps sheet covers the
full width of the external monitor in projected mode.
- Create a new class to hold all the properties that need to be
overridden. Set this class as part of DP buider.
- Override all props that are overridden for isTwoPanels.
- Update isTwoPanels to override using the new class in DP constructor.
Flag: com.android.window.flags.enable_taskbar_connected_displays
Bug: 414342881
Test: m
Change-Id: Ia035620c96c5a8912b99314014d4b19a125c7c5c
Remove com.android.launcher3
.enable_show_enabled_shortcuts_in_accessibility_menu flag and
references from the codebase
Fix: 415679751
Flag: EXEMPT. Cleanup
Test: OverviewMenuImageTest
Change-Id: I3a7b58b7c3fe4c6c3a5750fd1e851909630e80ff
> This allows the whole workspace model to be contained in itemIdMap instead of spread across multiple data containers
> Deprecating extraItems, all non-workspace data should use separate repositories
> Design: http://go/launchermodel-re-arch?#heading=h.5y8n4r164d5s
Bug: 390572144
Test: atest PredictionUpdateTaskTest
Flag: EXEMPT refactor
Change-Id: I886d0a8d5bbbf9f5c2054d4a2442bf03f9c4eab5
* There are race conditions and weird breakages when
we try to go to home/recents while split apps are being
animated so we disable for now.
Test: Manual
Bug: 391894192
Flag: EXEMPT bugfix
Change-Id: I0350a5124d72fab9d98f81d6ab5369bd790c16b1
Basically the same places we were notifying expensive frames.
Test: forrest perf suites
Flag: com.android.launcher3.all_apps_blur
Bug: 410973453
Change-Id: Ifb8ee7010e0faacc9ccc21076fc8614f335e2863
Current implementation fails but doesn't give error message on what caused failed.
Bug: 413665268
Test: Unit test
Flag: EXEMPT BUGFIX
Change-Id: Iedbd18bb37c0e4d1ac8b86d426d469ddc5fe163f
The test don't run yet in presubmit, first I will have the NexusLauncherE2ETests
target ready and then I will add it to the presubmit.
Bug: 324261526
Flag: EXEMPT test only
Test: atest NexusLauncherE2ETests
Change-Id: I4daa204ec735456c481b0682ca518da381af7bb7
Allows a subclass to follow the same pattern of using the device
grid to stipulate the layout params.
Bug: 415259527
Test: Manual, Unit
Flag: EXEMPT bug fix
Change-Id: I6afe9bbb1aba8132bdcbee92e1dca33e1243f4bd