-
Notifications
You must be signed in to change notification settings - Fork 64
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
Carousel component blocking the page transition #19
Comments
Hi @elzdave, |
Hello @vadimkorr , I'm using Inertia.js as routing library, together with Laravel framework. So, I make two pages, Homepage.svelte and AboutUs.svelte, together linked using Inertia.js. In the Homepage.js, I use this Svelte carousel to show image carousels on my homepage. When I try to navigate to AboutUs.svelte using Inertia link, the console.log throws error and the page simply can't move to AboutUs.svelte, but when I navigate from AboutUs.svelte to Homepage.svelte using Inertia, it can be done perfectly. I try to attach onDestroy event on carousel, but the error seems to be happened before destroy event, and when I temporary disabled the carousel, the navigation works as intended. I attached the following error log from the browser console
I currently didn't know how to attach debugger, please be patient :) |
@elzdave But I found this workaround: import Carousel from 'svelte-carousel/src/main.js'; // instead of import Carousel from 'svelte-carousel';
import 'svelte-carousel/dist/index.css'; Please check it out and let me know... |
I just want to report I was also having the issue using sapper and the workaround worked. To use in sapper:
Then:
|
Hello, after a week using this component, I found out that I couldn't do any page movements from page contain this carousel component to any other page. Don't really know exactly the problem, cause the browser console render unreadable stack trace, but when I temporarily commented this carousel component, I could go to other page and vice versa. Could you help on this? Thanks in advance!
The text was updated successfully, but these errors were encountered: