'swiper-button-disabled' class is not applied after initial render
See original GitHub issueThis is a (multiple allowed):
-
bug
-
enhancement
-
feature-discussion (RFC)
-
Swiper Version: 6.4.1
-
Platform/Target and Browser Versions: All.
-
Live Link or JSFiddle/Codepen or website with isssue: https://codesandbox.io/s/nuxt-swiper-qlvlg?file=/components/Swiper.vue
What you did
Created a swiper with items inside of it. Issue can be reproduced on default settings as well as with slidesPerView: ‘auto’. Option watchOverflow is set to true
Expected Behavior
‘swiper-button-disabled’ should apply to navigation buttons right after initial render of the swiper if the number of slides is smaller than container width
Actual Behavior
‘swiper-button-disabled’ is not applied after initial render
Issue Analytics
- State:
- Created 3 years ago
- Reactions:4
- Comments:9 (1 by maintainers)
Top Results From Across the Web
How to make swiper navigation disabled on activeIndex == 1
i set the initial slide on "1". i want to make the swiper navigation disable on index "1". can you please to figure...
Read more >Swiper API
Swiper is the most modern free mobile touch slider with hardware accelerated transitions and amazing native behavior.
Read more >fancybox3 · Documentation
You can install fancybox by linking .css and .js files to your html file. ... close button (if you have not disabled by...
Read more >Swiper - Relocating Previous and Next Buttons - CodePen
Insecure Resource. The resource you are linking to is using the 'http' protocol, which may not work when the browser is using https....
Read more >Swiper—Jumping on Page Load Resolved | by Aaron K.
This tutorial combines everything I learned from the preceding tutorials—moving previous and next buttons outside of Swiper's container to fix a ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
These workarounds don’t work, is this a recognized bug that will be solved? In that case I could temporary live with it…
Still experiencing the issue. My workaround for now: