Loading
Don't inherit task bounds from same instance in DMLPM
During phases of the DesktopModeLaunchParamsModifier calculations the current activity can be made visible before the bounds phase is complete. This causes it to be detected as a top visible freeform activity and since it matches the launching activity, is seen as a second instance where its bounds are inherited. However, since the bounds phase is not complete, the bounds it inherits are wrong. To prevent this, do not inherit the task bounds of an existing instance if it is that same instance (has the same task). Flag: com.android.window.flags.inherit_task_bounds_for_trampoline_task_launches Bug: 422364585 Test: atest WmTests:DesktopModeLaunchParamsModifierTests Change-Id: Id17a86110633cc00acfb14ce24736b7f95f4f591