mirror of
https://github.com/material-components/material-components-android.git
synced 2026-01-23 16:01:40 +08:00
b9d70d3d86
getPosTan, which calculates the translation of the conatienr bounds, no-ops if the startView doesn't move to a new position (when the startView and endView are top aligned and centered horizontally on one another). This was causing motionPathPositions, the int array holding the x and y of the animated bounds to never be initialized, defaulting to 0, and throwing off the bounds calculation. This CL updates the int array with actual default x and y values so when getPosTan no-ops, the motionPathPosition array contains the correct values. Resolves https://github.com/material-components/material-components-android/issues/1161 PiperOrigin-RevId: 319247326 (cherry picked from commit 3c9096d45128f11f3a84dca9f650373ff196cdce)