W3C home > Mailing lists > Public > www-style@w3.org > February 2013

Re: [cssom] Proposal for obtaining robust style information via Javascript - getStyle()

From: Simon Sapin <simon.sapin@kozea.fr>
Date: Fri, 01 Feb 2013 11:13:17 +0100
Message-ID: <510B953D.5060201@kozea.fr>
To: Boris Zbarsky <bzbarsky@MIT.EDU>
CC: "Tab Atkins Jr." <jackalmage@gmail.com>, www-style list <www-style@w3.org>
Le 01/02/2013 03:37, Boris Zbarsky a écrit :
> On 1/31/13 9:31 PM, Tab Atkins Jr. wrote:
>> >There are a lot of properties with values that don't become px until
>> >used-value time, for example.  This covers most properties with
>> >percentages, a number of properties with 'auto', and a smattering of
>> >other types of values.
> Ah, I see.  Hmmm....
>
> That of course raises the fun questions of what used values should
> return on nodes that have no boxes, or are not even in the document tree...

My understanding is that elements do not have used values, only boxes 
do. (At least that’s how WeasyPrint implements it.)

Also note that one element can generate multiple boxes (list item + 
maker, table + wrapper, fragmentation across pages, columns, …) and 
these boxes may have different used values for the same properties.

If you’re tempted to pretend that list item markers, table wrappers or 
pages can be ignored, consider the used height of a block fragmented in 
a multi-column context. Each fragment could have a different height.

Used values on elements do not make sense.

-- 
Simon Sapin
Received on Friday, 1 February 2013 10:13:44 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:05 GMT