| Summary | Use embedded [CSS] images |
| Queue | IMP |
| Queue Version | HEAD |
| Type | Enhancement |
| State | Resolved |
| Priority | 1. Low |
| Owners | slusarz (at) horde (dot) org |
| Requester | slusarz (at) horde (dot) org |
| Created | 08/08/2008 (6176 days ago) |
| Due | |
| Updated | 01/12/2010 (5654 days ago) |
| Assigned | |
| Resolved | 02/20/2009 (5980 days ago) |
| Milestone | |
| Patch | No |
Initial support for embedded image data in CSS
Beginning to implement
Ticket #7174. Eventually, all images should bemoved into CSS to allow for maximum caching.
http://git.horde.org/diff.php/imp/lib/IMP.php?rt=horde-git&r1=e751a9283893ad6559102e2bee9d529bf6ea4546&r2=624b959ec733846a46eea3515ac4eacdc4aeda1f
State ⇒ Resolved
in IMP). Once Horde_View architecture stabilizes, will eventually
move this to there.
http://cvs.horde.org/diff.php/imp/lib/IMP.php?rt=horde-hatchery&r1=e751a9283893ad6559102e2bee9d529bf6ea4546&r2=624b959ec733846a46eea3515ac4eacdc4aeda1f
Version ⇒ HEAD
Priority ⇒ 1. Low
Patch ⇒ No
Milestone ⇒
Assigned to Michael Slusarz
Summary ⇒ Use embedded [CSS] images
Type ⇒ Enhancement
State ⇒ Assigned
Queue ⇒ DIMP
Anticipated use would be to have a function that autogenerates
separate CSS file with images based on browser (IE vs. other
browsers). This CSS file could be cached so not only would it save
image requests, but that CSS file would only need to be grabbed once.
Use in DIMP initially since manipulating images may require javascript
(haven't worked out details yet).
Alternative is to rewrite image tags in Horde::img with data
information if browser supported and/or image below certain size. To
avoid costly file lookups/processing, the base64 representations of
the images could be cached server-side.