[webkit-dev] Accept- & Content-Resolution headers proposal

[Peter Speck]

On 07/06/2007, at 22:38, Maciej Stachowiak wrote:

> The only case that needs to be addressed better IMO is foreground  
> images via <img>. And that should probably be handled at the HTML  
> or CSS level, not the HTTP level.

But the html doesn't know (today) which dpi the display is using.  
When the server generates the html file to the client, it doesn't  
know the resolution either. So do you imaging adding Javascript  
properties to dynamically update <img> or do you want to add new  
attributes to the <img> tag?  Or should we replace all of them with  
<div>'s using backgrounds?

Rather than hacking <img> with special attributes for resolution, I  
consider "Accept-Resolution" a generalized solution rather than using  
one method for css backgrounds, another for <img>, and then another  
for <object> including images that Flash movies might fetch.


----
    - Peter Speck