Generic classnames collide about flexslider HOT 6 CLOSED

This is too generic to hold any weight. Many others have suggested the same thing, in the same way.

Think about how this affects how people use the plugin, with multiple sliders, and propose a suggestion. :)

from flexslider.

I know.
I edited this issue several times after posting (to put some examples in), but figured it were easier by examples.

Here goes some specific classnames:

• disabled
• no-js
• next
• prev
• slides

Specific other suggestions:

• By principle (and to avoid most conflicts), prefix all css classnames (fx. flex-slides, flex-next)
• Set fixed background-color and other most used styles on links, to avoid any template conflicts (fx. next/prev)
• Use !important statements for the important statements (fx. list-style)
• Use js variables for classnames in flexslider.js (makes it much easier for adoption into other templates)
• less inline styles in flexslider.js (more css classes)

I had a blast debugging the code when I converted it to a Joomla module. Some of these I fixed, but only just the ones to keep it running in single and multiple instances. :-)

from flexslider.

I like the ideas you're presenting. The issue will be balancing changes to the plugin without disrupting current implementations.

from flexslider.

I would like to use the flexslider inside the Joomla framework, and there is a div with an id in the template that is overriding the flexslider styling... Janich do you have any pointers?

from flexslider.

Clean up your FlexSlider CSS to make those styles more important. Use deeper selectors or !important (if absolutely necessary).

from flexslider.

FlexSlider 2 has a special treat for class namespacing mentioned here. Closing this issue.

from flexslider.