CSS aggregation breaks the Deco theme when viewed in Firefox, as discussed in http://drupal.org/node/309068
To reproduce:
- Install and enable Deco theme (http://drupal.org/project/deco) on a test site. Note its appearance.
- Turn on CSS caching.
A number of problems will now occur with the theme when viewed in Firefox, such as the font being wrong and odd spaces appearing in the visual layout.
Several people have reported this problem; I'm currently seeing it with Firefox 3.0.2 on Mac OS X 10.5.5, and the current version of Drupal 6 (6.4). We first encountered the issue on our company website, kosada.com, where we're using our own modified version of the Deco theme, but I have personally verified the problem with a clean install of Deco on a test site. The kosada site is running in apache 2.2.2, PHP 5.1.6, fc5. My test site is running in apache 2.2.9, PHP 5.2.6, fc9.x86_64.
The problem seems to be related to the @import calls used in the theme. There are two, both in style.css; they import layout.css and icons.css in the same directory. If these calls are commented out, and the code from those files is copied into style.css where the @import calls used to be, then the theme works as expected with CSS caching. This hack workaround is currently in use on kosada.com. I was under the impression that the patch from http://drupal.org/node/113607 should have addressed this specific problem with @import calls, but apparently it's still an issue.
Comments
Comment #1
jwolf commentedBoth calls to layout.css and icons.css should be placed in the theme's .info file (deco.info) and not an @import call in the main stylesheet.
I think this is more a Deco theme specific issue than a Drupal issue; moving issue to the Deco issue queue.
Comment #2
olarin commentedOk, it still seems to me like fixing this little snag in core would prevent future problems for other themes, but I don't fully understand how the css system works yet so I'm not going to argue the point. Since this has been declared a deco issue, I'm labeling it a duplicate of the aforementioned node http://drupal.org/node/309068, where a proper solution on the deco side has already been posted.