Do not call onConfigurationChanged for appBound position changes.
Since appBounds encodes both dimensions and positions, movement will cause a diff change. This happens in situations where the dimensions stay constant, such as dragging a PiP window around. To avoid flooding the client side with configuration changes, this CL checks whether the new configuration is equivalent to the existing configuration with the exception of the position of the appBounds before sending to the registered callbacks. Change-Id: I8fbc94458fd9ed3b39494c3587f25e704ec02a7d Fixes: 63927944 Test: bit FrameworksServicesTests:com.android.server.wm.AppBoundsTests Test: go/wm-smoke
Loading
Please register or sign in to comment