Re: [webkit-dev] Your opinion on a CSS proposal

2007-06-07 Thread Mark Rowe
On 07/06/2007, at 3:35 PM, 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.

Re: [webkit-dev] Your opinion on a CSS proposal

2007-06-07 Thread Windy Road
On 07/06/07, Mark Rowe [EMAIL PROTECTED] wrote: Anyone got any thoughts on how to deliver high resolution images to high DPI screens and low resolution images to low DPI screens. http://webkit.org/blog/55/high -dpi-web-sites/ mentions using CSS 3's media queries to target a portion of a

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Maciej Stachowiak
On Jun 7, 2007, at 6:27 AM, Nicholas Shanks wrote: It has been mentioned on the Safari WebKit development mailing list that a HTTP header which specified a document's target resolution would be useful to allow clients to negotiate for high-res or low- res artwork and CSS referring to such

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Maciej Stachowiak
On Jun 7, 2007, at 9:00 AM, Nicholas Shanks wrote: Sorry, Accept-Content: text/css, text/dsssl, text/xsl should of course have referred to Accept-Type :-) Actually it should have been Accept:. There is no Accept-Type header. - Maciej ___

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Rob Burns
Macej, I think you misunderstand the proposal. It does take scale factor into account. It also is meant to handle other cases (not just CSS). I do think you're right about the server advertising the possibilities, but that would probably complicate things a lot. In any case its better

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Andre-John Mas
Surely all of this becomes moot if we specify objects in terms of inches, cm or mm, all of which are already supported by css? A browser that interprets these 'absolute' units properly should already know what DPI the current environment is in, or have access to the necessary API to

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Rob Burns
On Jun 7, 2007, at 3:52 PM, Andre-John Mas wrote: Surely all of this becomes moot if we specify objects in terms of inches, cm or mm, all of which are already supported by css? A browser that interprets these 'absolute' units properly should already know what DPI the current environment

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Nicholas Shanks
On 7 Jun 2007, at 23:07, Rob Burns wrote: PS, again my suggestion is for the client to request specific pixel dimensions for the media not the ppi/dpi/cmpi) If the the UA is in an environment with multiple displays or multiple resolution output of any kind it can use that in determining

Re: [webkit-dev] Accept- Content-Resolution headers proposal

2007-06-07 Thread Nicholas Shanks
sorry for more spam people :-) a couple of things i don't have time to write about before i go to bed (tis gone 1am here) http code 300 is what i was wanting, not 406 or making up a new one http://www.w3.org/Protocols/rfc2616/rfc2616-sec10.html#sec10.3.1 the Suggest-Location param