Changes the criteria for showing caption on fullscreen tasks to check
if the device is a tablet based on screen size rather than using display
windowing mode.
Bug: 243671025
Test: Manual testing; launched fullscreen tasks on multiple devices with
and without desktop mode flag enabled.
Change-Id: I4550f040daef9c55edaaf42bcfc2004a23e6924f
WHen using shell-transitions, use a transition instead of
regular applyTransaction
Bug: 236047261
Test: use desktop-mode switch w/ shell-transit. observe an actual
transition.
Change-Id: I81f37d278420383f8b2b0f37cca8a398313705cb
UI crashing due to null windowDecor object being passed into
FullscreenTaskListener#giveWindowDecoration
Test: Manual Testing
Bug: 246637353
Change-Id: Iaefee1993e1477cb88ed34d8e94b5f24120152f1
For floating tasks the normal target size is too small to really
fit the task window, this allows the dismiss target to have a
different size set via a resource id.
Test: manual - override the size (in different CL), observe that
the target is at that size.
Bug: 237678727
Change-Id: I85edae739992662852d4cf40c250714a100a67bb
There's a bunch of useful stuff on TaskInfo (e.g. taskDescription and
background color). This exposes the existing method on TaskView so
users of TaskView can get this info.
Bug: 237678727
Test: none
Change-Id: I95e4bc37562a9f51b2cf6cec6d03889f57222e30
mManageEduView.show() requires a non-null BubbleExpandedView but getExpandedView() is declared as nullable.
Bug: 246824356
Bug: 246902054
Test: manual
Change-Id: I19d733ced80d121c7dab40936721c9cc8be1a12e
Some test automation will dismiss split-screen to launcher and then
immediately rotate the display. Currently, we can't properly
transactionalize the display-rotation, so it just gets squashed into
the existing collecting transition. The result is that the split-
screen handler expected just a split-screen transition but also got
a display-rotation.
This CL adds a mixed-handler case for rotation+split-screen that
stage-coordinator can then use to divide the transition into two
animations.
Bug: 244486556
Test: atest NexusLauncherTests:TaplTestsTaskbar#testLaunchAppInSplitscreen_FromTaskbarAllApps
Change-Id: I82b6a20155dc84e58ab95964da64c9c741f761d9
Same as the legacy app transition, we want to play the app customized
animation if there is no AE split.
We don't support app customized animation when there is AE split yet to
make the animation consistant.
Bug: 207070762
Test: atest WMShellUnitTests:ActivityEmbeddingControllerTests
Test: atest WmTests:TransitionTests
Change-Id: I68348cd650b9dbc8c39ef8d22a171d128e196882
Same as the legacy app transition, we want to play AE animation if all
changes are in Task with embedded activity
Bug: 207070762
Test: atest WmTests:TransitionTests
Change-Id: I66c5c083a517b3254d647c7335264eba8837f0cd
After I1a0c4d17, the expanding task will first be resized to fullscreen
then reparent to TDA after the divider bar fling animation finished. If
the expanding app is expanding to two pane mode, the resuming of the
second activity might be skpped due to the task in another side of the
split is already empty and invisible.
Update the drag-to-dismiss flow to reorder the expanding task on the top
of dismissing task. So the content in the dismissing side won't flicker
during the dismissing transition and the activity resume won't be
skipped in the expanding side.
Fix: 243368173
Test: atest WMShellFlickerTests
Test: atest WMShellUnitTests
Test: put Settings and Chrome in split screen,
drag divider bar to dismiss Chrome,
verified the expanding transition won't timeout
Change-Id: Id16c1d9b4849d5f600de9524ffebb91aba73a721
With legacy transition, we capture a screenshot of the reparent child,
and attach it to the parent surface (in WM Core), and then animate the
parent in handler.
With Shell transition, we also need to do the same (in WM Shell) to
screenshot the reparent child, and animate the parent using the child's
change info. Otherwise the child animation will be cropped.
Bug: 207070762
Test: manual
Change-Id: I52b5c839343864b4179e5c35c33343bc282bc189
Make sure pip screen size animates to normal
or maximum size depending on the current width
when a double tap occurs
Test: manually reproduced steps in the bug listed
Test: atest WMShellUnitTests:PipDoubleTapHelperTest
Test: atest WMShellFlickerTests:ExpandPipOnDoubleClickTest
Bug: 232173973
Change-Id: Ia8ec8696fddd236f992803451f44457e974069ac
Exit split if the side stage no longer has children. We should invoke
flingFinishedCallback even if there is no need to run animation when
fling divider to dismiss.
Bug: 244540465
Test: Drag Chrome to create multi-instance in split screen repeatly
Change-Id: I101044515c366287e37951a32a1b57618f1c8f3e
Not very sure root cause but it caused by we changing to using
ILegacyTransition from normal remote animation callback.
Rollback to previous implementation for fixing this.
Fix: 246513837
Test: manual
Test: pass existing tests
Change-Id: I5fdde8a2304423153f60163d64c2f1ba2e642468
Make sure the open/close a pair of activities act as one.
Cleanup unused adapter that was introduced for scaling animation, which
is replaced with x coordinate animation in T.
Bug: 19847347
Test: manually verify the animation with Shell transition
Change-Id: I5a34c2cf163f2a330e4c8111c16f8125bd5c2db5
This prevents erratic movements caused by animations that update layout each
frame, effectively reporting new keep clear area bounds every frame and
triggerring the movement multiple times. This will now wait for the keep
clear areas to stabilize before moving away.
Can be customized via system property.
Video before: http://recall/-/g8x7ZkgdfbqscttAA9wzl9/hwr0OrO4Pq8cvLw9bgwLff
Video after: http://recall/-/g8x7ZkgdfbqscttAA9wzl9/bGTKo0oqCKUwtvBdBYOB9w
Bug: 183746978
Test: manually, e.g. open PiP and slowly swipe up to go to overview, which
causes Hotseat to animate away triggering keep clear areas changed multiple
times, but the PiP moves only once
Change-Id: I2214e2250fb3cace8fee117285fd8ffbd27a3870
The DisplayLayout#stableInsets was set according to navigation bar
height and not get updated when TaskBar becomes visible.
Video: http://recall/-/aaaaaabFQoRHlzixHdtY/dPuTSbBuAgjfyKiliwzo2Q
Bug: 198644965
Test: Open another app with PiP present and move it around, see Video
Test: atest WMShellUnitTests:PipControllerTest
Change-Id: I4db1446de0cb257e26d34985d294908cfe692967
It was just a thin wrapper and thus unneeded abstraction.
Additionally, the mixed-handler is for general mixing, so
wrapping it in a name for just one combination is confusing.
Bug: 244486556
Test: Tests pass (meaning it still works)
Change-Id: I7a02f803fa421bbec02344d479d1d90ea741e155
Currently, the SplitscreenEventLogger is declared as private final and
initialized in constructor of the SplitScreenController and not used
anywhere else in the SplitScreenController. Moved the initialization to
the StageCoordinator and removed the field from SplitScreenController.
Bug: 245650570
Test: atest SplitTransitionTests
Test: atest SplitScreenControllerTests
Test: atest StageCoordinatorTests
Change-Id: Iedc8893982f3bc4ba4c41f6a394f5fdf39098a99
Merged-In: Iedc8893982f3bc4ba4c41f6a394f5fdf39098a99
Add unit tests for creating GroupedRecentTaskInfo objects and the
parcelling logic.
Bug: 244348395
Test: atest GroupedRecentTaskInfoTest
Change-Id: I10c97e91f164a45c3ed17935a820c5ed168e8305
- ACTION_DRAG_ENTERED does not actually have location data, and
ACTION_DRAG_LOCATION may not always be sent, which results in no
target being computed prior to the DROP. Since the DROP event
also has location data, we should update in that case as well.
Bug: 234653212
Test: atest TaplTestsTaskbar
Change-Id: I1f7657a95a4f124d98fc0da78b8a3ac2237f91f6
