W3C home > Mailing lists > Public > public-html@w3.org > May 2011

RE: Adaptive images

From: Leonard Rosenthol <lrosenth@adobe.com>
Date: Tue, 31 May 2011 06:48:41 -0700
To: Karl Dubost <karld@opera.com>
CC: Henri Sivonen <hsivonen@iki.fi>, "public-html@w3.org" <public-html@w3.org>
Message-ID: <D23D6B9E57D654429A9AB6918CACEAA98064C20D6D@NAMBX02.corp.adobe.com>
Correct.  And that's fine for web/server-hosted content.

However, consider an EPUB3 file where there is no negotiation going on.  So you'd (most likely) need something in the <img> tag that would list the alternatives and then have those connected (via id/name) to CSS queries so the UA would know which one to pick.

Leonard

-----Original Message-----
From: Karl Dubost [mailto:karld@opera.com] 
Sent: Tuesday, May 31, 2011 6:04 AM
To: Leonard Rosenthol
Cc: Henri Sivonen; public-html@w3.org
Subject: Re: Adaptive images


Le 31 mai 2011 à 08:39, Leonard Rosenthol a écrit :
> Images would be in the content/HTML, but the choice of which one would be in the CSS....

hmmm :) let's make it clearer. An IMG element with an URI.

<img src="http://example.org/foo"/>

I do a GET on http://example.org/foo

which gives the image depending on the Accept Headers, I can receive things like

Content-Location: foo.jpg
or Content-Location: foo.png
or Content-Location: foo.svg

If the browser was sending along the size of the screen with the first HTML request, it would be possible to have 

Content-Location: foo-big.jpg
or Content-Location: foo-medium.jpg
or Content-Location: foo-small.jpg

and/or the format variations of it.

In this scenario you do not need to put a list of all images in the content. The negotiation takes care of it.


-- 
Karl Dubost - http://dev.opera.com/

Developer Relations & Tools, Opera Software

Received on Tuesday, 31 May 2011 13:50:18 UTC

This archive was generated by hypermail 2.3.1 : Monday, 29 September 2014 09:39:25 UTC