#CSS

I think I'm missing something, but why exactly do we want to combine all CSS into a single file? Currently these CSS files are split into separate libraries (although node.module.css is in 2 different libraries) which are added in different parts of the CMS depending on where they're needed. Combining all CSS into 1 file will mean adding CSS to places that it's not needed. Isn't it better to only add it where it's needed?

We also have many themes overriding or extending these libraries to add their own CSS, we would have to very carefully coordinate releases between all of these otherwise there will be visual regressions. Furthermore, it means contrib would have to have a new major/minor targeting the specific core release this is changed in.

The effort doesn't seem worth it IMO, what are we trying to gain here? Even though the CSS is all admin-ish related, it's for very different use cases.

$ grep -ri IE11 --exclude-dir="node_modules" --exclude-dir="assets" core
core/themes/claro/js/tableselect.js:        // is preferable, but not supported by IE11.
core/themes/claro/js/tableselect.js:          // Determine add/remove with ternary since IE11 does not support the

Made an issue for this, 📌 Remove IE11 Support from Olivero Active