kenwheeler
Different .min.js and .js
When I used slick in my most recent project and when my code was integrated with AEM we noticed that the slick.min.js and slick.js files had different code for the slick load functionality. The slick.min.js file was behaving as expected and the slick.js was not. So we just unminified the slick.min.js and used that instead of slick.js. Please look into this issue and resolve it at the earliest so that others will not face the same issue.
we see the same issue here... slick renders elements differently (adding extra div elements in slick.js but not in slick.min.js). this breaks our code because we expect the elements to be rendered in dev/production builds in the same way
Same here.
slick.js adds additional divs around slides, slick.min.js - does not.
it looks like the min.js is stuck at version 1.8.0, so it's missing a few commits. So as a workaround, you can probably just minify slick.js yourself
Reverse situation here: slick.min.js breaks centerMode, while slick.js centerMode works: the minified version add a width: NNNpx;transform: translate3d(-NNNpx, 0px, 0px). The value of NNN is width - something_not_identified.
Similar to fgm, slick.min.js isn't working correctly for me, but slick.js is.
For info, my issue was with asNavFor not syncing when scrolling. It was scrolling about 20% further than expected, so by the time image 5 was displayed in the top slider, the thumbnail had already scrolled past.
Suffering from the same issue with Slick. Is there any update on this as it is almost a 5-year-old issue.
