W3C home > Mailing lists > Public > www-style@w3.org > June 2010

Re: [css3-text-layout] New editor's draft - margin-before/after/start/end etc.

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Tue, 01 Jun 2010 09:52:18 -0400
Message-ID: <4C051092.1010909@mit.edu>
To: Håkon Wium Lie <howcome@opera.com>
CC: "L. David Baron" <dbaron@dbaron.org>, MURAKAMI Shinyu <murakami@antenna.co.jp>, David Hyatt <hyatt@apple.com>, www-style list <www-style@w3.org>
On 6/1/10 3:59 AM, Håkon Wium Lie wrote:
>    - DDAs are mapped to their respective properties as soon as the
>      computed value of 'writing-mode' is known; thereafter DDAs --
>      their values and existence -- can be forgotton

Which just means that you have to keep track of _specified_ values for 
DDAs but not computed values.  Which is what Gecko and Webkit seem to do.

>    - there is no DOM access to DDAs (I hope, the draft doesn't say)

Why not, if they have specified values?

> This undertanding is supported by [2]:
>
>   >  For UAs supporting only horizontal writing, *-before, *-after,
>   >  logical-width and logical-height are simply aliases of *-top, *-bottom,
>   >  width and height respectively. No costs needed.

That seems like an optimization based on pre-converting on the specified 
value level due to knowing what computed writing directon will be.  That 
optimization is, of course, not compatible with DOM access to the 
specified values, so I'm not sure it's a valid optimization.  Unless the 
specified-value behavior of these properties is _very_ weird.

-Boris
Received on Tuesday, 1 June 2010 13:52:59 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:28 GMT