Retina.js: Retina graphics for your website

Post by WiseWeasel » Sun, Apr 22, 2012, 5:51 AM UTC

WiseWeasel wrote: post #99

ryannielsen wrote: post #96

Earlier quoted context omitted.

Yep, a solution is still needed for content images. That's their notation. Imagine having to do that for every image ever, when they're all just filename + 2x resolution key + filename extension. Totally asinine. Developers should just be able to pick a single page-wide filename key for all their 2x assets, and the browser will know to look there. You assume the developers can guarantee all image assets will be 2x. F…

No, the better solution would be to add support for: This would alert the browser of the likely presence of 'filename_x2.ext' when it sees img tags, and it would fall back with a second request for 'filename.ext' in case it's not found. This seems relatively easy to implement (especially for web developers), and degrades gracefully on older browsers. Then, a more fleshed out version accounting for the scenario you de…

Sorry, that should be '2x', not 'x2'. The img '2x-res' property could also be used to provide an asset-specific 2x-res filename key as such:

If we wanted this to affect the image asset requested by the CSS background-image and border-image values as well, then a new CSS property would be required for flagging 2x-res active or not and an asset-specific 2x filename key. But its use would be vastly superior to -webkit-image-set, as you could just do this:

  .class {2x-res: "@2x"}

or:

  .class {2x-res: "false"}

The only limitation is that these 2x assets must share the same filename with the 1x, except for the addition of a 2x key at the end of the filename. However, that seems to be what people are already doing simply to keep track of their assets, and it's much easier to sell me on this imposition than on having to redo all my CSS in the most redundant and painful way imaginable.

Re: Retina.js: Retina graphics for your website

Re: Retina.js: Retina graphics for your website