[webkit-dev] Your opinion on a CSS proposal
Hi, Sorry in advance if this is the wrong place/way to ask this. I recently posted on the www-style list a proposal for allowing the 'font-size' CSS property to have a value of 'auto': http://lists.w3.org/Archives/Public/www-style/2007Jun/0016.html The basic idea is that when font-size: auto is used, the browser would calculate the font-size based on the element's width margins and padding. A javascript mockup is available at: http://windyroad.org/static/resolution-independence/ What I would like to know, if you can spare the time, is what you, the webkit developers, feel about this proposal. I'm not involved in any browser development, so I don't know the implications such a proposal would have if is at all feasible. Thanks for your time, -- Tom Howard http://windyroad.org ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Your opinion on a CSS proposal
On 06/06/07, David Hyatt [EMAIL PROTECTED] wrote: Except that the width of an element can depend on the font size. And in those situations (say a floated element), specifying font-size: auto would be invalid and should be ignored. Your idea is interesting, but it can't really be defined using font- size. It's more of an after-the-fact adjiustment based off the calculated width of a block. So let me rephase the question. Do you think the effect I'm trying to achieve should be specified via CSS or Javascript? If the former, do you have any suggestions on how? Cheers, -- Tom Howard http://windyroad.org ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Your opinion on a CSS proposal
On 06/06/07, Rob Burns [EMAIL PROTECTED] wrote:
I think its an interesting idea. However, perhaps it would be better
to have an additional property that wouldn't conflict with the font-
size property. Something like font-size-transform (to avoid conflict
with font-size-adjust though this could still cause author
confusion).
I thought about this as well, but when I was developing the demo I
kept thinking What I really need is a way in CSS to tell the browser
that I don't care what the font size is, just make sure the line
length is X characters, whatever the width of the column is. This is
why I thought of font-size: auto
hmm... maybe line-length is a better option. e.g. adjusting my previous example
body {
width: 100%;
line-length: 62.5em;
}
#main-column {
width: 80%;
}
#secondary-column {
width: 20%;
}
Thoughts?
Cheers,
--
Tom Howard
http://windyroad.org
___
webkit-dev mailing list
webkit-dev@lists.webkit.org
http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Your opinion on a CSS proposal
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 webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
Re: [webkit-dev] Accept- Content-Resolution headers proposal
Hi, Does Apache support Feature negotiation as specified in RFC 2295 (see http://www.ietf.org/rfc/rfc2295 )? If so, is there any documentation related to this (I couldn't find any)? If not, are there any plans to support this portion of the RFC? FYI the back story to this request is from a discussion regarding having images served to a client dependant on its resolution and/or viewport width. Normal browsers may get an the image as 600px across, small screen devices may get an image that is 150px across and browser requesting the image for printing purposed may get an image that is 1200px across. I was able to create a type-map file for the images as follows: URI: image URI: image-1200x1000.jpg Content-type: image/jpeg; qs=0.9 URI: image-600x500.jpg Content-type: image/jpeg; qs=0.5 URI: image-300x250.jpg Content-type: image/jpeg; qs=0.25 URI: image-150x125.jpg Content-type: image/jpeg; qs=0.1 Apache would (correctly) perform server side selection to pick the variant with the highest qs, however I could not find any way of specifying features (such as DPI) for each variant, that would allow a lower qs variant to be selected based on a appropriate request with Accept-Features (e.g. Accept-Features: dpi=[70-100]). Cheers, -- Tom Howard http://windyroad.org ___ webkit-dev mailing list webkit-dev@lists.webkit.org http://lists.webkit.org/mailman/listinfo/webkit-dev
