Closed jakemauer closed 12 years ago
That wouldn't be a problem with Jammit -- that'd be a problem with your CSS compressor (in this case, probably YUI), right?
In any case, I don't see why you'd inline images before, given that Jammit can inline them perfectly well for you:
Whelp, I'm a dummy. I didn't really think through how Jammit works and didn't even think to check YUI Compressor. Turns out this bug was fixed in a recent build (2.4.7) which has yet to be pulled in to YUI-Compressor-Ruby. As for not using Jammit's inline-ing, I'm hamstrung by how the site I'm working on was built. Currently we serve 5 separate stylesheets based on site location and can't load everything into a single sheet due to overlap issues. (I know this is bad, but I can't change it ATM) so I have to use Compass' inline-ing.
I'll use a custom version of YUI-Compressor-Ruby and be on my way. Thanks for the quick reply!
I'm using guard with Compass and Jammit for my project. If I use Compass' inline-image function to produce a data-uri in the CSS, Jammit fails to compress my CSS. If I remove the data-uri line, compression works fine.
I don't want to use Jammit's built in data-uri functions because I only want to use it for specific images to keep our CSS file size down.
An example of the CSS output by Compass that causes the error: