React-slick: Setting rows property to < 1 or null crashes the app and tab.

[blwsh]

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.

[silicakes]

Same here.
I've tried to use rows: 0 in order to avoid the regression caused by adding an extra row div.
The page crashes.

[GioLogist]

Can confirm, happening for me as well - latest stable version.

[edzjins]

Can confirm too, happens on the latest stable version, it's acually unusable for me at this point because of it.

[matenka-andrii]

Same here. Guys is there some way to fix that behavior?

[webdevpchoi]

Confirm this issue is still occurring. Has anyone found a fix for this yet? Having a redundant div is driving me bonkers.

[LuisPerez94]

Confirm this issue is still occurring

[blwsh]

1 year old this issue. They grow so fast. If I get a moment I’ll try put in a pull request.

[l3dger]

Has a fix for this been released yet?

[samturner3]

This issue is also blocking solving https://github.com/akiran/react-slick/issues/1539

We can't set the height to be the same for all sides based on the tallest slide without rows: 0

[partyconfetti]

Still crashes and took a lot of time to figure out in a big project...

[blwsh]

Dw! The world will end soon, we can mark this issue as “low priority”

[TheHacker66]

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.

[vsdmoraes]

Same here, sometimes crashes, sometimes open a debugger.
Any updates?