Similar to WCT#setAdjacentRoots, but can be called with fragmentTokens
in case the TaskFragments may not be created yet.
Bug: 190433129
Change-Id: I41dd515fb9722ea6e95d0c3fb040cc0d196ad78d
Test: atest WmTests:TaskFragmentOrganizerControllerTest
NEW_TASK flag was added by ATMS when #startActivityInTaskFragment
is called because the activity was started without source record.
Bug: 193846941
Test: starting CCT in sample app
Change-Id: Ida26034324f7ff761f1e688403d78959a01f010d
Currently it will not receive stage visibility changed callback
after display info changed, the divider will not show even if it
has re-initialized.
Fix this by add applyVisibility call when display info changed.
Fix: 194159070
Test: active stage split and rotate phone
Change-Id: I2b9d6849300bc8a594cdbe658a7f7a663fd949a7
When Shell transition is enabled, some launcher tests failed because the
keyguard exit remote animation never invoke the finish callback.
The expect flow is:
1. Dismiss amount changed from 0 to 0.1+ to trigger the keyguard going
away transition.
2. Dismiss amount changed from 0.1+ to 0.3+ to finish the keyguard exit
remote animation.
However, in presubmit test, the dismiss amount may changed from 0.0+ to
1.0 directly. When it happened, there is only a trigger to start the
transition, but never trigger the change event to call the finish
callback, which blocked the Shell transition.
The idea is to also check the current dismiss amount when the keyguard
going away transition reach to the controller.
Bug: 183993924
Test: atest PromiseIconUiTest
Change-Id: I95951385130578f45df0837200cc7e88d89edd34
The drag down animation didn't do the transition
to the full shade visually, so things would look
out of place.
Fixes: 191282610
Test: drag down while bypassing
Change-Id: Icdd62155f3762621c1046ed5271476ec0b4e2635
* changes:
Add the log for new supported accessibility button type 'Accessibility Gesture'
Update the supported type in ACCESSIBILITY_BUTTON_MODE according to navigation gestural mode or button mode
Add a supported type 'gesture' under ACCESSIBILITY_BUTTON_MODE
The stack trace in b/194344478 and b/194280568 is actually from the
preceding ActivityThreadTest test, which does not fail but does crash
certain test cases after that.
Since we may set a start delay on the content overlay fading out
animation, there is chance that onTaskVanished happens before it is
actually started. It's also possible that onTaskVanished happens during
the content overlay fadeout. This CL should have addressed both cases.
Bug: 194344478
Bug: 194280568
Test: atest --iteration 5 \
ActivityThreadTest#testHandlePictureInPictureRequested_overriddenToEnter \
ScreenshotTests#testScreenshotSecureLayers \
TaskStackChangedListenerTest#testTaskChangeCallBacks
Change-Id: I81c0622966df32e02db7cb5aa3cd42d7c4af735e
