Skip to content
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

Closed
daviedR opened this issue Aug 18, 2016 · 7 comments
Closed

Intrusive Slick Carousel CSS #424

daviedR opened this issue Aug 18, 2016 · 7 comments
Assignees
Labels
bug Indicates a bug with one or multiple components.

Comments

@daviedR
Copy link
Contributor

daviedR commented Aug 18, 2016

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:

.elementor-widget-image-carousel .slick-loading .slick-list {
    background: #fff url("../images/ajax-loader.gif") center center no-repeat;
}

instead of

.slick-loading .slick-list {
    background: #fff url("../images/ajax-loader.gif") center center no-repeat;
}

What do you think?

@joshmarom
Copy link
Contributor

Thanks for the feedback.
It will be considered.

@joshmarom joshmarom added the bug Indicates a bug with one or multiple components. label Aug 18, 2016
@arielk arielk assigned arielk and unassigned kobizz Aug 18, 2016
@daviedR
Copy link
Contributor Author

daviedR commented Oct 31, 2016

Hi guys,

Somehow the changes were reverted back to the unwrapped version, not sure whose commit. Could you wrap the slick CSS back?

@arielk
Copy link
Member

arielk commented Oct 31, 2016

@daviedR We didn't have any change at all. What exactly is the problem?

@daviedR
Copy link
Contributor Author

daviedR commented Nov 1, 2016

@arielk you have revised this before, on this commit:
(88b0a7d)

However, looks like the commit was not merged or perhaps reverted due to some changes on your folder structures (you added dev folder on assets). In current version the wrapping classes you have added in that commit are gone. For instance:

The revised _slick.scss file with the proper wrapping classes (from your commit):
https://github.com/pojome/elementor/blob/88b0a7d31b7ce767838776adea243a7622b7cf83/assets/scss/frontend/_slick.scss

Current _slick.scss file:
https://github.com/pojome/elementor/blob/master/assets/dev/scss/frontend/_slick.scss

Please put back the revised version with the wrapping classes. Your slick CSS broke my native theme's slick styles.

@arielk
Copy link
Member

arielk commented Nov 1, 2016

You can go through the line 274 and see the correction of the bug:
https://github.com/pojome/elementor/blob/master/assets/dev/scss/frontend/_slick.scss#L274

@daviedR
Copy link
Contributor Author

daviedR commented Nov 1, 2016

Hmm, I think you need to entirely wrap all slick classes, because you have custom styles under the:

//
// Slick Elementor Theme
//

and

//
//  Custom Style for Elementor
//

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:

image

But when Elementor is activated, it broke into like this:

image

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.

@arielk
Copy link
Member

arielk commented Nov 1, 2016

@daviedR Please try this pull #784 and let me know is solve your bug

@KingYes KingYes closed this as completed in cf4b03a Nov 2, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Indicates a bug with one or multiple components.
Projects
None yet
Development

No branches or pull requests

4 participants