-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
Intrusive Slick Carousel CSS #424
Comments
Thanks for the feedback. |
Hi guys, Somehow the changes were reverted back to the unwrapped version, not sure whose commit. Could you wrap the slick CSS back? |
@daviedR We didn't have any change at all. What exactly is the problem? |
@arielk you have revised this before, on this commit: However, looks like the commit was not merged or perhaps reverted due to some changes on your folder structures (you added The revised Current Please put back the revised version with the wrapping classes. Your slick CSS broke my native theme's slick styles. |
You can go through the line 274 and see the correction of the bug: |
Hmm, I think you need to entirely wrap all slick classes, because you have custom styles under the:
and
They are not default CSS from original Slick package. In my case, I use Slick for my theme's slider. without Elementor enabled it looks like this: But when Elementor is activated, it broke into like this: If you wrapped all your slick CSS to affect your own slider only, my theme's styles woul work normally. Of course, I can create a higher priority styles to override your plugin CSS, but Elementor's slider styles would be the one which broken this time. It's very important to keep them separated, please wrap your Slick custom styles. |
Hi guys, is it possible to add highe selector to your custom defined Slick carousel CSS in
frontend.css
? Some themes might also use Slick carousel for their own elements and your CSS broke the styles.I know you pasted the original Slick default CSS and then combine them with your own custom CSS. I think the custom CSS declarations should have higher level selector.
For example, it should be:
instead of
What do you think?
The text was updated successfully, but these errors were encountered: