summaryrefslogtreecommitdiff
path: root/api/api_test.go
diff options
context:
space:
mode:
author Riddle Hsu <riddlehsu@google.com> 2024-12-31 15:51:20 +0800
committer Riddle Hsu <riddlehsu@google.com> 2024-12-31 06:00:06 -0800
commitaf1b500aa6c01a6e683f9bf1bea7017a6f1aa511 (patch)
tree8e1407d5628b03e2c4e8e652c45be78a6713a96d /api/api_test.go
parentf7c4dc872c75fe812d523f42da22d1c42851016a (diff)
Avoid empty TaskFragment removal affecting playing transition
A transition will apply the finish transaction from buildFinishTransaction when it finishes. But if there is a parallel transition runs and finishes before the previous transition, the layer assignment may have conflict. Even if the transition doesn't contain changes (shell will abort it), its finish transaction is still applied by shell's Transitions#onFinish. E.g. when recents transition (allow parallel) is running, an app with embedded activities deletes its empty TaskFragment when its activity is removed by recents (swipe up task view). By not collect invisible TF and not return WCT effect for empty TF removal, applyTaskFragmentTransactionLocked can abort the empty transition in WM core if the effect is none and the transition does not contain participants. Fix: 381466040 Flag: EXEMPT bugfix Test: TaskFragmentOrganizerControllerTest# \ testApplyTransaction_enforceHierarchyChange_deleteTaskFragment Change-Id: Ibe86b36ea675330d63b90dda30332d0d4220489d
Diffstat (limited to 'api/api_test.go')
0 files changed, 0 insertions, 0 deletions