-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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
navigation
changes are not reflected in Swiper instance
#4458
Comments
navigation nextEl, prevEl doesn't support refs, it accepts HTMLElements or string with CSS selector of elements. |
@nolimits4web |
Check this thread #3855 maybe it has solution for you? |
Sadly, it doesn't. Moreover, it contains workarounds, not bug fixes. Anway, I cannot call |
As you didn't provide live example, I have no idea what you are doing, but |
I thought the bug is clear, but as you ask, I've added example.
I see no property on swiper that would inform whether navigation has been initialized or not. |
…ustom elements added after initialization fixes #4458
👆fixed, will be available with next update on a days |
What You Did
Navigation changes are not recognized by swiper component. If you set
navigation: false
and later change to specific HTML element refs, it will not work, even after callingupdate
on swiper instance.Example: https://stackblitz.com/edit/react-ayg1t2?file=src%2FApp.js
Expected Behavior
When I change props, component does update accordingly.
Actual Behavior
I change
navigation
and nothing happens, even with forcedupdate
.The text was updated successfully, but these errors were encountered: