Changes between Initial Version and Version 1 of Ticket #21019, comment 21
- Timestamp:
- 06/21/2012 03:31:43 PM (13 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #21019, comment 21
initial v1 7 7 > Then we get an image, and then some JS can convert img.fs-img's src to -2x.jpg (or _2x, or @2x), and then they become sharper. It's progressive JPGs all over again. 8 8 9 This wouldwork well for the screenshots on the About screen, but not for most of the other places. The problem is that most images are loaded as css backgrounds (all the sprites), so there aren't <img /> tags for them.9 This may work well for the screenshots on the About screen, but not for most of the other places. The problem is that most images are loaded as css backgrounds (all the sprites), so there aren't <img /> tags for them. 10 10 11 11 Another (big?) drawback of using JS is that replacing the images at DOM ready leaves the screen "imageless" for couple of seconds. What happens is the low-rez images start to load together with the html, at DOM ready all half-loaded low-rez images are replaced with the high-rez. That makes the browser send another set of requests for them before the requests for the low-rez images have completed. So now we have double the number of image requests.