Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.Problem/Motivation
All CSS is divided into module/admin/theme (aka MAT) files. This division allowed theme developers to be selective over which CSS they choose to load, functional CSS or "look and feel" CSS.
After #2489460: [Meta] Move module.theme.css files to Classy or Seven, theme developers no longer need to have this distinction at the file level, they can choose to use Classy as a base theme. We can split the CSS files into self-contained component files, which means they are easier to maintain, find, and load granularly.
Proposed resolution
Split and rename the system.module.css and system.theme.css files in modules and Classy into separate component files -> [component-name].css
Remaining tasks
User interface changes
None
API changes
None
Comments
Comment #1
LewisNymanComment #2
davidhernandezComment #3
andypostis this still valid?
Comment #4
davidhernandezJust thinking off the top of my head, I think we can still split up the files in core but leave them alone in Stable for BC. We'd have to be careful with the libraries though and make sure they get correctly overridden by Stable.
Comment #5
andypostBut keeping them in stable will require to override them in seven, isn't it?
Is there issue to discuss how to proceed with css refactorings after 8.0?
Comment #6
davidhernandezThe split can happen, but I don't think we can move them. Or we would have to move them to Stable to free them from core. Anything more than that is probably a non-BC break.
Comment #7
davidhernandezCorrection, they should already be in Stable so there is nothing to move. We can split the files that are in Stable. That would be a breaking change, regardless of libraries. People can target the individual files.