You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Vanilla has an unspoken style rule that component class names should not be mixed (i.e., an element should only have classes from one component, and possibly is-<theme> modifier).
<!-- Unofficial "recommended" usage --><divclass="row--50-50"><divclass="col"><divclass="p-section"><p>Text</p></div></div></div><!-- This happens quite a bit in sites --><divclass="row--50-50"><divclass="col p-section"><p>Text</p></div></div><!-- This can also happen --><divclass="row--50-50"><divclass="col"><pclass="p-section">But this also works</p></div></div>
This introduces inconsistency between projects and could lead to broken styling. We should document this (perhaps at the site-wide level) and inform users about the recommended usage more officially, so that this convention can be more formalized.
The text was updated successfully, but these errors were encountered:
Vanilla has an unspoken style rule that component class names should not be mixed (i.e., an element should only have classes from one component, and possibly
is-<theme>
modifier).For example (adapted from thread by @petesfrench ):
This introduces inconsistency between projects and could lead to broken styling. We should document this (perhaps at the site-wide level) and inform users about the recommended usage more officially, so that this convention can be more formalized.
The text was updated successfully, but these errors were encountered: