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
{{ message }}
This repository has been archived by the owner on Jan 27, 2021. It is now read-only.
I'm experiencing a weird issue when using using this lib with ReactCSSTransitionGroup.
I have a transition that is working fine in conjunction with react-router (simply fading page transitions).
However when using the transition group for a carousel, the app crashes (unpredictably and intermittently when changing slides).
If I remove winstore-jscompat and continue to use the transition group, the app crashes with the dangerous dom insertion issue.
So far, the only workaround I've found is to render all of the carousel items to the DOM, and then apply an active class modifier - this is not good for performance.
It seems to me the thinking with adding these security rules in metro was not great - they cause problems with the frameworks people actually use to create app like experiences. Thanks for your efforts with this library to try and address them
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
I'm experiencing a weird issue when using using this lib with ReactCSSTransitionGroup.
I have a transition that is working fine in conjunction with react-router (simply fading page transitions).
However when using the transition group for a carousel, the app crashes (unpredictably and intermittently when changing slides).
If I remove winstore-jscompat and continue to use the transition group, the app crashes with the dangerous dom insertion issue.
So far, the only workaround I've found is to render all of the carousel items to the DOM, and then apply an active class modifier - this is not good for performance.
It seems to me the thinking with adding these security rules in metro was not great - they cause problems with the frameworks people actually use to create app like experiences. Thanks for your efforts with this library to try and address them
The text was updated successfully, but these errors were encountered: