Bug: 195699800
Test: dismissing stage split with divider bar will fling the divider bar
smoothly to the edge of the screen before split been dismissed.
Change-Id: Ic3bb2d9bc6da82773b7818c70dc535a5cea8e437
WM team starts to remove functionalities that were made for unmanaged
tasks so take this step 1 to avoid regressions from this type of
changes.
Also remove UNSUPPORTED_WINDOWING_MODES because ShellTaskOrganizer can
handle all windowing modes now.
Bug: 192310211
Bug: 165794880
Bug: 165794636
Test: Maximize, drag and resize freeform windows.
Change-Id: If130b449fe6cf37c39f0e1424e4f23cdb2d33dd5
Root cause:
1. Design change "tap app to exit" -> always being true, and settings
remove this option.
2. Tuning performance, due to 1, no longer listens to the key change,
so we remove the listener.
Solution:
Change getSettingsTapsAppToExit() API to return default TRUE.
Bug: 195629000
Test: Build ROM and factory-reset to test
Test: atest WMShellUnitTests
Change-Id: Id3c265258ed28f7e0aa54505c339671885d28fa7
Shell owns the whole display rotation animation now. So, we
can just provide enough information for it to decide when
seamless is requested/appropriate. The default behavior (when
not explicitly animating) is already a jump-cut/seamless, so
just skip the rotation animation if we are doing seamless
Bug: 194693472
Test: atest SeamlessAppRotationTest ShellTransitionTests
Change-Id: I64748f5910c04784fd9818818b029fa5f1339c6c
When finishing the last activity in a container that has dependent
containers, make sure to delete those in addition to just finishing
activities. This will ensure that containers with activities from
different apps will be properly cleaned up.
Bug: 195108809
Test: Launch a container to side with 'finishSecondaryWithPrimary'
configuration, finish the primary container with swipe from side.
Test: Do the above for activities in different apps.
Change-Id: I746055fd02894d8221cace10d556992e2dba31b5
This allows applying split rules to activity start requests for
different processes and covers APIs like 'startActivityAsUser',
not requiring app developers to use dedicated APIs to start to side
instead.
When the client organizer observes a new activity being started, it
creates a new TaskFragment first and modifies the activity start
options to target that container.
Bug: 194140227
Bug: 190433398
Test: Manual, using reference implementation and sample app.
Change-Id: Ice3de8ec725d327266ec38052129b4158608855e
- onPipTransitionStarted()
Use InteractionJankMonitor.Builder to setup with PIP task's
leash and dispatch to begin() with CUJ_PIP_TRANSITION
- onPipTransitionFinishedOrCanceled()
End CUJ_PIP_TRANSITION when the transition either finished
or canceled.
Test: atest WMShellUnitTests
Test: atest SystemUITests
Test: record systrace through perfetto.dev
Bug: 169221267
Change-Id: I9f94ddde7f0dd48d50d50313ba517b919f0d8d25
On phone we use 60% of the screen which is huge on
tablet. This change uses 30% of the screen for the
flyout on large screens & enforces a minimum for
that value.
Test: manual - get a long message in a bubble on a
tablet, it should have similar width
as it does on phone.
Bug: 186776550
Change-Id: I500c566edd9941dc2bd149692eaf95c6e6f4aa61
- manage button should be inset from the expanded view edge
but the menu should be flush with expanded view edge.
- button size is smaller (36dp instead of 40dp)
- more padding (16dp above / below on both tablet & phone)
- diff colour N1-800 instead of N1-900
Test: visual 1 - expand a bubble and look at 'manage' button
2 - tap on the button and look at the menu
3 - do 1 & 2 on tablet & in RTL & on phone
landscape
Bug: 183658858
Change-Id: I4b5ffc26602b72ee28d26476fc222df3e2e1e80b
Activity#onCreate is called before receiving the TaskFragment
appeared event in the client process. So, the client split
controller created another split and resulted in unexpected
behaviors.
Bug: 194860679
Test: start activity to side
Test: wm presubmit
Change-Id: Iac34bd39376940c5c0224c8687ad9858a4190e20
