Currently, whenever a CSS file is added that uses a media query in the options array it creates a new aggregation group when processed. This introduces a frontend performance issue on sites that use many different media queries as it potentially raises the number of aggregates drastically. For example, if a media query dependent stylesheet is added in the middle of a group of CSS files the current behavior causes the creation of 3 aggregates instead of just one (pre-media-query-stylesheets / media-query-stylesheets / post-media-query-stylesheets).
Ignore the media query option of stylesheets that have 'preprocess' set to TRUE when CSS aggregation is enabled and write the media query into the CSS aggregate instead (wrap it around the string content of that file when building the cache).
Tests, maybe.
None. It doesn't have an effect on the weighting of stylesheets either.
Closed: outdated
9.5
It affects performance. It is often combined with the Needs profiling tag.
Issue related to Drupal on mobile devices.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
I had opened 🐛 Aggregation creates two extra aggregates when it encounters {media: screen} in a library declaration Fixed four years later back in 2016 without realising it was a duplicate, and that issue got committed to 10.0.x, so marking this one outdated.