[whatwg] Resolutions meta tag proposal
aral at aralbalkan.com
Fri Jul 2 06:28:14 PDT 2010
I'm an interaction designer/developer, not a rocket scientist. :) A
meta tag, I can easily add. If you start talking about HTTP headers,
you've lost me.
i.e., this is meant to be a pragmatic, easy-to-author solution.
On Fri, Jul 2, 2010 at 2:13 PM, Marques Johansson <marques at displague.com> wrote:
> And what if the image was named "images/flower" (using the accept header to
> send a jpg vs png vs gif) instead of "flower.jpg". The browser would need
> to have rules about how to rewrite the name of the file. I think "@" in the
> filename would break the many Dos 6.22 based web servers ;-).
> I don't think a single element with a single attribute can handle this
> What about an HTTP header like:
> Accept: image/*;ppiratio=2
> This would allow the server to send the correct images for that client or
> return a 307 to the rewritten filename as the server deems fit. A new
> Accept property doesn't seem to require changing any specs. I'ld like to
> think that image/*;q=x could be used in some way for this.
> On Fri, Jul 2, 2010 at 8:39 AM, Aral Balkan <aral at aralbalkan.com> wrote:
>> I just submitted a proposal for a new meta tag to flag that
>> high-resolution images are available and should be loaded in place of
>> low-resolution ones for users with high-PPI displays (like the new
>> iPhone 4's Retina display).
>> Please see:
More information about the whatwg