Problem/Motivation

Overlay module adds both of it's js files with preprocess=1

For every page on a Drupal site, there is potentially a with-overlay and without-overlay version - this counts for both the admin pages displayed in the overlay, and the child page displayed under the overlay.

The result of this, is that the number of css/js aggregates in the same group as overlay's js doubles. I've just seen 78 aggregates with either overlay-parent.js or overlay-child.js in them.

In this case the aggregation does more harm than good - since the page viewed in the overlay would have been a cache hit on the existing aggregate then one additional js file to load (cached or uncached), whereas instead we get a duplicate aggregate which is less likely to be cached.

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

Comments

catch created an issue.