Closed (works as designed)
Project:
Drupal core
Version:
7.x-dev
Component:
base system
Priority:
Normal
Category:
Bug report
Assigned:
Reporter:
Created:
28 Sep 2010 at 00:59 UTC
Updated:
28 Sep 2010 at 04:18 UTC
I think there is no need to load the modules .css files using the .info files because they are loaded by default.
| Comment | File | Size | Author |
|---|---|---|---|
| redundant-stylesheets-loaded-in-info-files.patch | 2.46 KB | munzirtaha |
Comments
Comment #1
ksenzeeI'm not sure I understand. Where else are these .css files being loaded?
Comment #2
bleen commentedhuh? I dont understand. Can you give an example?
(cross posted with ksenzee ... but we're both confused so thats ok)
Comment #3
munzirtaha commentedUmm! It's was me actually who got confused and didn't check enough. I found many modules are not using the .info file to load the stylesheet and thought it's loaded by default like the *-rtl.css files. Now, after a second thought I found that some modules e.g
block, color, profile, locale, openid, overlay, profile, simpletest, system, taxonomy, update load their *.css files using drupal_add_css() function,
whereas others like:
aggregator, book, comment, field, forum, node, poll, search, simpletest, user
load the *.css files from the *.info file. Any reason for this inconsistency?
Comment #4
bleen commentedthere are reasons ... if you read through #769226: Optimize JS/CSS aggregation for front-end performance and DX you'll see that a lot depends on what css files should end up in the aggregated css file for anon users and whet files shouldn't
Comment #5
munzirtaha commentedThanks for the clarification