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

Re: margin-inline-start and friends

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 9 May 2013 15:10:30 -0700
Message-ID: <CAAWBYDCggTwYFrGDMzxOCSMb1Ua4uLmK-vRo2y7-B6kjoXdHyg@mail.gmail.com>
To: "L. David Baron" <dbaron@dbaron.org>
Cc: Simon Sapin <simon.sapin@exyr.org>, fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
On Thu, May 9, 2013 at 3:03 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Thursday 2013-05-09 14:59 -0700, Tab Atkins Jr. wrote:
>> On Thu, May 9, 2013 at 2:56 PM, Simon Sapin <simon.sapin@exyr.org> wrote:
>> > Le 09/05/2013 23:51, fantasai a écrit :
>> >> You need to cascade and compute writing-mode and direction first,
>> >> then cascade the logical properties. Antenna House Formatter has
>> >> an implementation of this, and helped us to specify it.
>> >
>> > Ah, I see. Interesting. Did implementers notice some runtime cost in doing
>> > the cascade in two passes?
>>
>> That's not necessary, under David's proposal.  You can cascade them
>> together and then determine at computed-value time what property
>> affect which sides.
>
> No, it does require doing the cascade separately.  But Gecko already
> does cascading separately for groups of properties, so it's fine for
> us.

Hm, can you explain why?  As far as I can tell, it should work fine to
cascade them together, so long as you're okay with the "real" values
only showing up at computed-value time.

~TJ
Received on Thursday, 9 May 2013 22:11:17 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2013 22:11:18 UTC