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
I'd like the mountOnEnter/unmountOnExit props to be optionally splatted to the <Transition /> elements via switch parameter; otherwise set as the default behavior. Transitions in their current state still reserve space in the DOM when their in is false, causing awkward spacing issues when using multiple transition boundaries for a particular result.
This is becoming more necessary for my particular project - I have a div within the transition boundary that requires session data that doesn't exist at the time the component is mounted by default. The data is provided by a prior transition and then waits for a separate event handler to receive data from an endpoint before it is allowed to move on.
So, what is happening is, the div is running the waiting loop as soon as the parent component is mounted, which causes the entire parent component to fail to load because it is waiting on data it can't possibly have received by this point. Mounting behavior should resolve this.
Summary of the new feature / enhancement
ref: Forum#12177
I'd like the mountOnEnter/unmountOnExit props to be optionally splatted to the
<Transition />
elements via switch parameter; otherwise set as the default behavior. Transitions in their current state still reserve space in the DOM when theirin
is false, causing awkward spacing issues when using multiple transition boundaries for a particular result.Minimal reproduction:
Proposed technical implementation details (optional)
No response
The text was updated successfully, but these errors were encountered: