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
Motion is unexpectedly applied to mountNode element when rendering an OverlayDrawer inside a container, and using position="end". I observed this in my own app, and thought perhaps it was something with my own styles having an effect. To eliminate that possibility, I opened the code example Overlay Inside Container in StackBlitz, added position="end" to the OverlayDrawer component and was able to reproduce the issue.
To explain what is happening in the gif below, when the "open drawer" button is clicked, the drawer appears on the right side of the container, and then the overlay begins to slide in from the left. But as the overlay slides in, so does the mountNode element. So it's almost like the motion being applied to the overlay element is also being applied to the mountNode element.
I used the Animations tab in Chrome Dev Tools to inspect and slow the animation speed to 10% so its easier to observe. The issue remains when the animation speed is 100%.
Workaround
Setting the surfaceMotion slot to null, on OverlayDrawer, appears to eliminate the issue.
Expected Behavior
Motion should only affect the overlay and not the mountNode element.
Component
Drawer
Package version
9.56.8
React version
18.3.1
Environment
Current Behavior
Issue
Motion is unexpectedly applied to mountNode element when rendering an
OverlayDrawer
inside a container, and usingposition="end"
. I observed this in my own app, and thought perhaps it was something with my own styles having an effect. To eliminate that possibility, I opened the code example Overlay Inside Container in StackBlitz, addedposition="end"
to theOverlayDrawer
component and was able to reproduce the issue.To explain what is happening in the gif below, when the "open drawer" button is clicked, the drawer appears on the right side of the container, and then the overlay begins to slide in from the left. But as the overlay slides in, so does the mountNode element. So it's almost like the motion being applied to the overlay element is also being applied to the mountNode element.
I used the Animations tab in Chrome Dev Tools to inspect and slow the animation speed to 10% so its easier to observe. The issue remains when the animation speed is 100%.
Workaround
Setting the
surfaceMotion
slot to null, onOverlayDrawer
, appears to eliminate the issue.Expected Behavior
Motion should only affect the overlay and not the mountNode element.
Reproduction
https://stackblitz.com/edit/shd9svh6
Steps to reproduce
Are you reporting an Accessibility issue?
None
Suggested severity
Medium - Has workaround
Products/sites affected
No response
Are you willing to submit a PR to fix?
yes
Validations
The text was updated successfully, but these errors were encountered: