We've already fixed it on our end but wanted to flag as it didn't seem like the best approach for a module to have CSS that applies outside of its own scope.
Our custom CSS is already applied to our own defined classes and ids. No other module we use overrides it. What happens here is that when Slick loads there is a CSS rule that overrides all .view, .view .view-content, .block .view, .block .view .view-content classes with a custom rule. That simply didn't seem right to us.
We might have a very specific use case and I understand it might not be worth fixing as it doesn't seem to affect many people. We simply assumed it was worth flagging as it might affect others at some point.
My guess is that you might be able reproduce this bug without any custom css but using blazy grid display and get similar results but I could be wrong. In any case, we'll stick to a fix in our CSS for now.
Thanks for the quick response. Full page screenshot attached, the top element is Slick Carousel (loaded as a block) but the affected element is a part of a Drupal view used for the frontpage.
We have our own set of classes and CSS, the display:block property basically overrides a display:grid property.
privacyint → created an issue.