Should the Conditional Styles always show up in the code AFTER the active theme CSS? I'm trying to use this module with the Omega theme, and it seems as though my IE-specific styles are being rendered before the theme CSS, which in effect, seems to make them useless. I'm just trying to track down where this can be fixed, through this module or through Omega. In other themes, it seems to be rendering the right order, so it makes me think it's a theme-specific issue.

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

minneapolisdan’s picture

Status: Active » Closed (works as designed)

I figured this out, it's just that this module shouldn't be used with the Omega theme. See this post for more info, http://drupal.org/node/1263750

hkirsman’s picture

Version: 7.x-2.0 » 7.x-2.x-dev
Status: Closed (works as designed) » Needs review
FileSize
726 bytes

IMO this module should work with Omega.

I think we should set more weight so it would work with all themes.

I've set group and weight to 9999 so the files would load after all the other stylesheets in Omega theme. I understand that grouping is ment for aggregation but for this module every stylesheet is packed separately anyways so it doesn't harm the download speeds for user.

Lower group and weight numbers work too but 9999 is more safer. It could be 99999 or 999999 too I guess.

I've attached a patch. What you think?

kclarkson’s picture

Title: Placement of Conditional Styles in Code: Fix for Omega » Placement of Conditional Styles in Code: fix door Omega

I found this issue after hours of trying to add the conditional styles to my .info file.

I have applied the patch and so far everything looks good.

kclarkson’s picture

Title: Placement of Conditional Styles in Code » Placement of Conditional Styles in Code: fix for Omega
kclarkson’s picture

Title: Placement of Conditional Styles in Code: fix for Omega » Placement of Conditional Styles in Code: Fix for Omega

Typo