1) the optimization of this module on Ie ies the same of core or better?
2) how a module can understand on which code I'm working on?

Comments

antlib’s picture

antlib commented

Yes, was wondering about question #2 myself...

Stan

willazilla’s picture

willazilla commented
Title: difference from core indetails? » difference from core in details?

Actually I am wondering how to configure the module, designate which CSS I am currently testing. Or, is it plug and play?

matteoraggi’s picture

matteoraggi commented

On module frontpage is written: "The fix for this on production sites is to simply enable the “Optimize CSS files” option on admin/settings/performance. " so just plug, enable and it pay by itself. Please if you have some issues, open one new if your is not about the original argument.

johnalbin’s picture

johnalbin
they/他
Primary language English
Location Taipei, Taiwan
commented
Status: Active » Fixed

The optimization used by this module is exactly the same as that used by core. It simply leaves the theme’s CSS files out of the aggregated CSS file. So after configuring your website to use the “Partial optimization for theme CSS development” option on admin/settings/performance, each page will load a single aggregated CSS file for all the module stylesheets and will load each of your theme’s stylesheets individually.

I was planning on adding a “Partial optimization for module CSS development” option (which would aggregate all theme CSS, but leave module stylesheets alone), but haven't gotten around to it. That would be the answer to #2. How does it know which code I'm working on? It doesn't; you would have to tell the module if you are working on module CSS or theme CSS.

willazilla’s picture

willazilla commented

Thank you so much for building this module! As well as the concise answer. I am swimming in some pesky IE issues, and looking forward to some relief.

Status: Fixed » Closed (fixed)

Automatically closed -- issue fixed for 2 weeks with no activity.