At the moment, this module works on non-aggregated CSS files.
I'm not sure that is really necessary.
It seem if you are concerned about reducing http requests [the aim of this module], then you'll have that enabled.

If that assumption is made, then coding could be a bit easier.
The work only need to happen when the aggregated css file is saved.

On the User interface, the setting to generate Data URIs could be disabled/hidden until the CSS aggregation box option was enabled.

Comments

dmitriy.trt’s picture

dmitriy.trt commented

I agree, there is no need to parse non-aggregated CSS. I'll remove this part of code.

About UI... maybe there will be no UI, see http://drupal.org/node/849352#comment-3186034

dmitriy.trt’s picture

dmitriy.trt commented
Status: Active » Fixed

Fixed in latest CVS

http://drupal.org/cvs?commit=394188

Status: Fixed » Closed (fixed)

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