-
Notifications
You must be signed in to change notification settings - Fork 52
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
Failed to execute 'removeChild' on 'Node' #41
Comments
Can you share your component? |
I'm experiencing the same issue intermittently. I'm have the following relevant dependencies:
my render method looks as follows:
I've tried setting Any advice? |
Same issue. |
@JPStrydom @GChin12 Could you provide a reduced test case in code sandbox? I feel like your issue has something to do routing, but I cannot reproduce this. You can modify this one link to suit your case. |
Just FYI, I reverted back to a vanilla Flickity setup and my issue is fixed. |
@yaodingyd Why do you suspect it's a routing issue? When I remove the Flickity component, the issue disappears completely. If I have some time I'll try to reproduce the issue in the sandbox. |
@JPStrydom I'm saying it could be the conditional rendering resulted from routing. Again, I'm just speculating. A reduced test case would really be helpful. |
Cool, I'll have a look in the morning. But say it is the routing, how would we approach the issue? |
It's not. We are currently facing the same problem with a pretty bare-bones implementation (no dependencies beside It seems like it has something to do with the |
Same here, any solutions? |
I ended up using Nuka Carousel - it's not as flexible, but it does the job. |
Thanks for providing an alternative, even better with MIT license! Have a great day! |
This thread has no useful information for actual debugging work of said error. Closing for now. |
When component needs to re-render, this happens. |
Issue is tracked at #49 |
Issue should be fixed with release of 3.1.0 |
Thank you very much @yaodingyd ! |
Since no activity is present since 2018, I will share the way I managed to fix this error in my case. Imagine we have the following situation:
Switching over different videos pages, So the way I fixed this was just adding a key to the
|
I already have added the key but nothing seems to chage, I am still having the error. |
Be sure that your key for slider/carousel is changing correctly depending on the value of slides it includes. |
Hi, I just setup a PoC using this library and all went OK following the setup guide, the carousel works perfectly and the implementation was really easy.
I''m however getting an error when transitioning back-and-forth between the view where the carousel lives and other ones:
I am using a mix of angularJS + uiRouter and React right now, but I'm not sure it has to do with the stack itself. I wonder if I need to make something happen on
componentWillUnmount
to make sure all references to DOM elements used by flickity are purged (flickity.destroy()
?).From the stack trace the error seems to stem from
FlickityComponent
.The text was updated successfully, but these errors were encountered: