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
Setting rows property to < 1 or null crashes the app and tab. #1254
Comments
Same here. |
Can confirm, happening for me as well - latest stable version. |
Can confirm too, happens on the latest stable version, it's acually unusable for me at this point because of it. |
Same here. Guys is there some way to fix that behavior? |
Confirm this issue is still occurring. Has anyone found a fix for this yet? Having a redundant div is driving me bonkers. |
Confirm this issue is still occurring |
1 year old this issue. They grow so fast. If I get a moment I’ll try put in a pull request. |
Has a fix for this been released yet? |
This issue is also blocking solving #1539 We can't set the height to be the same for all sides based on the tallest slide without |
Still crashes and took a lot of time to figure out in a big project... |
Dw! The world will end soon, we can mark this issue as “low priority” |
We almost defeated covid but we can't have a fixed slider in 2021.. I'll see if I can do it and open a PR. |
Same here, sometimes crashes, sometimes open a debugger. |
Same here crashes every time. The issue is also without |
Has anyone found a solution here? This is affecting issue kenwheeler/slick#3581 too. |
The app will crash if you set the sliders row property to anything < 1 or null. The row property sometimes needs to be set to 0 so slick doesn't wrap your slide content in a pointless div according to a resolved issue on the slick github repo.
To replicate just add
rows: 0
to your settings object.The text was updated successfully, but these errors were encountered: