deliver zero specificity CSS

[AndyOGo]

Are you reporting a bug or a feature?

• Feature

Expected Behavior

It's expected that our consumers don't have to deal with CSS specificity hell originating form the patterns-library itself.

The goal is to avoid .adjoining.classes or .parent .classes and only get the desired CSS by

• proper cascading order
• @media queries

Let's discuss how we want to approach this and if we need common rules.

I think the downside is:

• same modifier/state classes have to be added to multiple DOM nodes (performance decrease)
• bigger maintenance and more efforts needed for implementation

Actual Behavior

States and some modifiers increase CSS specificity slightly.

[LucaMele]

We always should provide one level of specifity (class ONLY selector, no children no ID, no TAGS). This helps the consumer of the library if they have to override styles

[LucaMele]

closing as new plib version is live. If issue is with v2 still relevant, please re-open