-
Notifications
You must be signed in to change notification settings - Fork 150
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
Uncaught TypeError on transition end when component re-renders #175
Comments
+1 I'm having the same issue. react version: 16.2.0
|
Ok thanks, will take a look ASAP |
The same on:
|
+1 same here
do you have an idea about when it will be fixed ? |
Unfortunately, I'm quite busy at the moment and I will not be able to prioritize/fix this issue |
Hi. I'm having the same issue.
As @tomzmtl reported this error probably caused by the DOM element referenced not existing anymore at the time the toastr is dismissed. Do you have any idea if it's could be fixed? |
I believe this issue is already fixed, can you please tell me which version you're using @NataSemka ? |
Because of inactivity I will close this issue but feel free to reopen in case anyone feels that this has to be addressed. |
I'm getting the following error when a toastr is dismissed (manual and auto):
The
null
value here isnode
inonCSSTransitionEnd
.I think it is caused by the DOM element referenced not existing anymore at the time the toastr is dismissed. This issue started occuring when we started implementing a mix of toastr + view transition in our app. I figure the toastr node is being re-rendered at view transition, hence the loss of reference.
I don't know if there is a way to work around this, otherwise maybe toastr should check for the existence of the reference when
onCSSTransitionEnd
runs to avoid those errors.Here is a sample of my component:
The text was updated successfully, but these errors were encountered: