- First commit to issue fork.
We expose many class attributes in templates and other layers (for example preprocess), but it's never clear which classes are needed for JavaScript functionality, leaving themers in the dark if they want to slim down their markup and not break JS.
Add CSS classes for JavaScript functionality. Classes will use the original name and be prefixed with .js- and be added to the existing class (in Classy) for separating design and functionality.
<div class="foo"> -> <div class ="js-foo foo">
<div class="foo"> -> <div class ="js-foo">
This is a step along the way to using data attributes, but even if we don't get to data attributes it's still an improvement.
See child issues.
None for themes extending Classy. Possible visual changes to themes not extending Classy.
n/a
Active
11.0 🔥
It involves the content or handling of Cascading Style Sheets.
A change record needs to be drafted before an issue is committed. Note: Change records used to be called change notifications.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.