diff options
| author | 2025-02-06 07:12:24 +0000 | |
|---|---|---|
| committer | 2025-02-06 18:27:02 +0000 | |
| commit | 7183185d556a916f1b70fbe2124892cc23a770a3 (patch) | |
| tree | 033373ad8850bb416443f91d4d5f18033c863f03 /api/coverage/tools | |
| parent | 45d73de73eacd0a4c3e6a50c110fa1ff1e95ac52 (diff) | |
Ensure that split is always notified of recents transition finishing
- In ag/31399901 we added a mixed handler callback which notifies split
  via onRecentsInSplitAnimationFinishing() when the recents transition
  is finishing along with direct information about whether the
  transition finished to home or to the app.  However, currently there
  are recents mixed transitions that actually aren't handled by recents
  (ie. they can be handled by split + remote) for which
  onRecentsInSplitAnimationStart() is still called (it still does
  things like attach the divider to the transition to be animated).
  In such cases, we should remove the bookend-transition gating logic
  from the calls added in ag/31399901 and ensure that we always notify
  split of the recents transition finish if it's not already notified
  by the recents transition handler.
  Note that this is only affected by enable_recents_bookend_transition
  because previously with the flag off the legacy call
  onRecentsInSplitAnimationFinish() would always be called in the mixed
  transition logic.
- Also add some more logs for future debugging along this path
Fixes: 393226708
Bug: 391486839
Bug: 346588978
Flag: com.android.wm.shell.enable_recents_bookend_transition
Test: atest TaplTestsTaskbarSearch#testLaunchSearchWebSuggestionInSplitscreen
Test: atest TaplTestsTaskbar#testLaunchShortcutInSplitscreen
Test: atest TaplTestsSplitscreen#testSaveAppPairMenuItemOrActionExistsOnSplitPair
Test: atest WMShellUnitTests
Change-Id: Iab2225f454d9de80bdca0f0a958596ab2d6637ff
Diffstat (limited to 'api/coverage/tools')
0 files changed, 0 insertions, 0 deletions