After the removal of CSS classes from the core templates, many unnecessary HTML tags were left behind. They were not removed in the process of removing classes and other work, because removing them requires paying particular attention to any affect on the output.
Beta phase evaluation
|Issue priority||Normal because nothing is broken.|
|Unfrozen changes||Unfrozen because it only changes templates and possibly CSS which are both unfrozen.|
|Prioritized changes||The main goal of this issue is to improve themer experience.|
|Disruption||There should be minimal disruption.|
Go through each core template and remove any unnecessary markup. This will require looking at the output to see if things shift around in unwanted ways. Various CSS files may also need checking. For example, if there is CSS like
.some_class > div > .some_other_class the CSS should be adjusted, or deleted.
Evaluation criteria, not set in stone but up for discussion:
- divs and spans with no additional attributes should be removed mercilessly unless they justify their existence.
- Semantic tags (footer, article, etc.) should be retained even if they have no attributes.
This child issue will tackle most of the core module templates. Other issues will be added to the parent meta to remove tags from system, views, and other places.
User interface changes
Two small visual changes in Stark.
block--system-branding-block.html.twig, before & after
link-formatter-link-separate.html.twig, before & after
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 95,220 pass(es). View
PASSED: [[SimpleTest]]: [PHP 5.4 MySQL] 95,107 pass(es). View