this is similar to an issue with views which was just resolved so that it can be optimized: http://drupal.org/node/642328 - is there a different issue for this module? it might not be important because the menu only shows up for certain users anyway ... not anonymous users where performance is a big deal.

Comments

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Version: 6.x-1.5 » 6.x-3.x-dev
Category: feature » task

We basically had the same reasoning like Views -- avoid separate aggregated CSS files for admin users, since admin_menu's CSS is loaded on all pages.

However, it's possible that this doesn't make sense in a broader scope, i.e. in case there are various modules that add admin-only CSS files, so a separate aggregate will be created anyway.

I'm not entirely sure, so leaving this open for discussion. A decision should ideally be based on live data of actual CSS aggregation files.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Title: admin_menu.css not preprocesssed, not optimized - is there a compelling reason? » admin_menu.css not aggregated - is there a compelling reason?
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Version: 6.x-3.x-dev » 7.x-3.x-dev
sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Active » Needs work

No discussion happened.

sun’s picture

sun
Primary language German
Location Karlsruhe
commented
Status: Needs work » Closed (works as designed)