You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Mobile
I haven't tested this on mobile but theoretically it should happen there too.
Open the bottom sheet.
Rotate the device (triggering a change in the screen dimensions)
Describe what you expected to happen:
A window/screen resize should not result in a change in the animatedIndex
Notes
I've done a little exploration on fixing this but I'm not super happy with any of my approaches or results. I've effectively tried to set a property in the component when a resize reaction takes place and then adding a conditional to check if a resize event is the responsible for triggering a recalc on the animatedIndex property.
If I could get some direction from someone who knows more about the library and the best path forward I'd happily do the implementation and submit a PR!
The text was updated successfully, but these errors were encountered:
Bug
When a resize event occurs such as a screen rotation (in native) or a window resize (in web) the bottom sheet index can change suddenly. This seems to be due to
animatedContainerHeight
being used in the calculation ofanimatedIndex
.Environment info
Steps To Reproduce
Web
Mobile
I haven't tested this on mobile but theoretically it should happen there too.
Describe what you expected to happen:
A window/screen resize should not result in a change in the
animatedIndex
Notes
I've done a little exploration on fixing this but I'm not super happy with any of my approaches or results. I've effectively tried to set a property in the component when a resize reaction takes place and then adding a conditional to check if a resize event is the responsible for triggering a recalc on the
animatedIndex
property.If I could get some direction from someone who knows more about the library and the best path forward I'd happily do the implementation and submit a PR!
The text was updated successfully, but these errors were encountered: