Could you provide a simple document with some text and links to help
those of us who are not familiar with concepts like:

* "CSS embedded images"
* "aggregated CSS"
* "data URI schemes"

It might help with adoption of this module if more people better understood
what it does and how it works.

Comments

jcarnett’s picture

I updated the description on the project page to try and explain exactly how this module works. I plan to add more information, such as benefits/drawbacks, but let me know if that clears it up at all.

Aveu’s picture

This definitely helps the casual module seeker to know what this module does without having to do research.
Thank you!

I am curious about something: The new description shows some CSS code something like this:

OLD LINK = url(images/menu-expanded.gif)

NEW LINK = url(data:image/gif;base64, [...data...])

Since the new link does not provide the actual filename how does the system fallback (i.e.: how does it know where to look for the image) when Embedded Images is not supported by a given browser other than the two IE browsers you have added CSS hacks for?

Also, how does the system fallback (i.e.: how does the page render) when the browser does not support CSS at all (or perhaps when a Firefox user opts to ignore supplied CSS and use their own local CSS formatting)?

philbar’s picture

Status: Active » Fixed

This module uses an IE hack by taking the "OLD LINK" and appending *html, and *+html to it, in addition to creating the "NEW LINK".

For example, you should see something like this:

body {
   background: url(data:image/gif;base64, [...data...])
}

*html body,*+html body {
   background: url(images/menu-expanded.gif)
}

Also, if people want to provide their own local style sheet, then they need to solve any issues they have on their own. They can use normal links to the images or embedded images, either should work.

Status: Fixed » Closed (fixed)

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