Fix the regression of PiP position in fixed rotation
This also fixes issue with rotating on tablets where PiP might go out of bounds. What happens is sometimes the rotation of screen has not issued the callback yet and onInsetsChanged gets called causing regression and mixing up all calculations based on the configuration change that is being applied too early. Basically ordering issue of callbacks. Bug: 254869973 Test: manually, tried with logs statements that confirmed it works as expected regardless of the order in which the events callbacks are received Change-Id: Ie1ac5e94559643028229c7829b35905b175425d2
Loading
Please register or sign in to comment