-
Notifications
You must be signed in to change notification settings - Fork 272
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dragging the message while its beeing auto closed recreates a non-closable toast message #531
Comments
Just identified the problem in a discussion thread dated 2021... Is this library still being actively maintained? It appears to have numerous open issues from 2020+. |
The same is also happening for me, is there any fix for that or not? I saw some commits for making it non swipeable does that fix the problem or anything . |
@mathvaillant Thank you, I appreciate your solution. I will use it in the meantime. However, this problem should be fundamentally fixed as non-visible elements remain in the background. |
@mleister97 can you share the solution here? |
can confirm that this issue is still reproduceable |
Guys, I solved the problem with this reply #299 (comment). You can modify node_modules with patch-package |
When dragging the toast slightly down (and hold it) and waiting for the autoclose feature to take effect, a second toast message appears unexpectedly. This secondary toast is non-closeable and disrupts the user experience. This issue should be addressed to ensure a seamless and expected behavior when interacting with toasts.
video5947004665152409660.mp4
The text was updated successfully, but these errors were encountered: