On Jun 7, 2007, at 1:11 AM, David D. Kilzer wrote:
Wasn't one of Hyatt's suggestions that the author of the web page
provide
references to both a low-res and a high-res image so that the
client (which
knows most about which one to use) may chose the correct one?
Dave
That sounds familiar. However, resolution specific content
negotiation would be better supported through a rev to the http
protocol. It could be done now with some javascripting or CSS media
queries (for CSS urls anyway), but by adding it to http, it could
just work with little effort on the author's or server admin's part.
Rob
Rob Burns <[EMAIL PROTECTED]> wrote:
Its not easy to do these days. In my opinion, this is one of the key
features needed for an HTTP 1.2 (along with event/change
notifications and a few other things). Apache can probably be
configured to do this, but I'm not sure that there's a way to easily
get the HTTP clients to request a particular resolution.
Take care,
Rob
On Jun 7, 2007, at 12:35 AM, Windy Road wrote:
On 06/06/07, David D. Kilzer <[EMAIL PROTECTED]> wrote:
You may be interested in these blogs as well:
http://webkit.org/blog/55/high-dpi-web-sites/
http://webkit.org/blog/56/high-dpi-part-2/
Thanks for the heads up. I did find them interesting.
Anyone got any thoughts on how to deliver high resolution images to
high DPI screens and low resolution images to low DPI screens.
Cheers,
--
Tom Howard
http://windyroad.org
_______________________________________________
webkit-dev mailing list
[email protected]
http://lists.webkit.org/mailman/listinfo/webkit-dev
