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
When this library is being used together with https://suid.io/, all material styles are lost on exit transition, because the <style> element in the <head> gets removed when the exit transition starts. Seems like SUID is cleaning house when it thinks the styled element is no longer in the dom (while it still is because of the ongoing transition).
Here's an example snippet. The described behavior happens when removing a message, which triggers the exit animation:
Should this be an issue here or in SUID?
I’m not sure what can be done here. Transition component doesn’t have a control over the disposal of the owner of existing branch, it only reacts to it.
I’m not sure what SUID could do either. If they remove the styles in a cleanup, they don’t have other options.
Both SUID and transition-group are separate libraries, and neither should special case one another.
The only common part between the two is solid, so this is where the solution needs to be introduced imo.
At least if the API of transition-group is to remain without change. Which is, I think, one of the goals of this library.
When this library is being used together with https://suid.io/, all material styles are lost on exit transition, because the
<style>
element in the<head>
gets removed when the exit transition starts. Seems like SUID is cleaning house when it thinks the styled element is no longer in the dom (while it still is because of the ongoing transition).Here's an example snippet. The described behavior happens when removing a message, which triggers the exit animation:
The text was updated successfully, but these errors were encountered: