commit a8ad5e8c9bb62f25baf1cf2310849dc0fde2585f Author: Christoph Burschka Date: Fri Jul 28 16:53:56 2017 +0200 Remove documentation on IE workaround. --- .../Drupal/Core/Asset/CssCollectionRenderer.php | 27 ---------------------- 1 file changed, 27 deletions(-) diff --git a/core/lib/Drupal/Core/Asset/CssCollectionRenderer.php b/core/lib/Drupal/Core/Asset/CssCollectionRenderer.php index 3550bcb2ee..611a7a3581 100644 --- a/core/lib/Drupal/Core/Asset/CssCollectionRenderer.php +++ b/core/lib/Drupal/Core/Asset/CssCollectionRenderer.php @@ -23,33 +23,6 @@ * files are for different media types. Non-IE browsers always download in * parallel, so this is an IE-specific performance quirk: * http://www.stevesouders.com/blog/2009/04/09/dont-use-import/. - * - * However, IE has an annoying limit of 31 total CSS inclusion tags - * (https://www.drupal.org/node/228818) and LINK tags are limited to one file - * per tag, whereas STYLE tags can contain multiple @import statements allowing - * multiple files to be loaded per tag. When CSS aggregation is disabled, a - * Drupal site can easily have more than 31 CSS files that need to be loaded, so - * using LINK tags exclusively would result in a site that would display - * incorrectly in IE. Depending on different needs, different strategies can be - * employed to decide when to use LINK tags and when to use STYLE tags. - * - * The strategy employed by this class is to use LINK tags for all aggregate - * files and for all files that cannot be aggregated (e.g., if 'preprocess' is - * set to FALSE or the type is 'external'), and to use STYLE tags for groups - * of files that could be aggregated together but aren't (e.g., if the site-wide - * aggregation setting is disabled). This results in all LINK tags when - * aggregation is enabled, a guarantee that as many or only slightly more tags - * are used with aggregation disabled than enabled (so that if the limit were to - * be crossed with aggregation enabled, the site developer would also notice the - * problem while aggregation is disabled), and an easy way for a developer to - * view HTML source while aggregation is disabled and know what files will be - * aggregated together when aggregation becomes enabled. - * - * This class evaluates the aggregation enabled/disabled condition on a group - * by group basis by testing whether an aggregate file has been made for the - * group rather than by testing the site-wide aggregation setting. This allows - * this class to work correctly even if modules have implemented custom - * logic for grouping and aggregating files. */ class CssCollectionRenderer implements AssetCollectionRendererInterface {