What's up!
In my situation, I'm attempting to utilize IE 7 conditional styles within the Code per Node CSS area.
The styles are for a block view, and so far are working great. All except the conditional CSS I've used, as it's commenting it out (in syntax highlighting, it turns it all yellow).
It makes sense why it doesn't work - you can't multiple style sheets in there, but is there a workaround for this you know of? What would be cool is to be able to add another CPN CSS, or JS, area!
Also, is it something you can hack in Code Mirror? Not sure if that makes sense, though.
Many Thanks,
jtreinau
| Comment | File | Size | Author |
|---|---|---|---|
| Screen shot 2011-06-23 at 9.35.39 AM.png | 25.3 KB | jeremiahtre.in |
Comments
Comment #1
jeremiahtre.in commentedComment #2
jeremiahtre.in commentedComment #3
joelstein commentedThough the module will allow you to save conditional comments, they are included in the CSS file, but not embedded in the page. It seems conditional comments are ignored when included in an @imported CSS file.
One solution includes adding option per content type to show conditional CSS fields, and then rendering these within conditional comments. Something like:
Another option includes changing the way this module works, and giving you the option to add a "code" field, choose which type of field it is (CSS, CSS IE7, JS, etc), and provide a way to "add another". Or, we could just abandon the current storage method, and totally convert to using true D7 Fields.
I'm not inclined to work on this one, but I'd gladly review a patch.
Comment #4
jeremiahtre.in commentedThanks for taking the time to look at this, joelstein!
You're right, that would be cool. For now, I think I'll just hang tough. Your module has really helped us, at Ashland University. Really great stuff.
I'll let my co-workers know about the patch offer, should they decide to go ahead with it!
Peace,
jtreinau
Comment #5
damienmckennaPostponing this indefinitely - like joelstein said before me, I don't intend to add this but will gladly accept patches. And yes, it would involve a major update of the module in order to handle this functionality.