Loading
Allow direct CHANGED_PIP_BOUNDS advancement
There are cases where direct advancement to PipTransitionState.CHANGED_PIP_BOUNDS makes sense. This for example applies to cases where a bounds change being scheduled gets aborted for some reason (say cause bounds remain the same). In these cases, we don't really wanna send these to be animated, so we don't wanna advance to CHANGING_PIP_BOUNDS, but we do wanna jumpcut to CHANGED_PIP_BOUNDS to allow interactions again and bring PiP into a valid idle state. Bug: 434137294 Bug: 433901438 Flag: EXEMPT bugfix Test: drag PiP to top corner multiple times to get invariant bounds Change-Id: Ib73d9faeeac2d7f0b7d15ea389729c48cc82464c