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 16:40:35 -0700
Message-ID: <CAAWBYDBV_pYNgPV3vbSy77Vk+h9o+BRGPcAW-MrtL6-pz8+=Wg@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 4:36 PM, L. David Baron <dbaron@dbaron.org> wrote:
> On Thursday 2013-05-09 16:19 -0700, Tab Atkins Jr. wrote:
>> On Thu, May 9, 2013 at 4:09 PM, L. David Baron <dbaron@dbaron.org> wrote:
>> > I should probably say this more clearly:
>> >
>> >  * for LTR, margin-start and margin-left must be cascaded together
>> >
>> >  * this requires that the direction be known before cascading margin
>> >    properties
>> >
>> >  * this means the cascade has two passes (which is what Simon was
>> >    asking about), with direction being done in the first pass and
>> >    margins (cascaded together) in the second pass
>>
>> I'm just not understanding why your suggestion at
>> <http://lists.w3.org/Archives/Public/www-style/2002Sep/0049.html>
>> requires this. :/  It looks like you can just cascade everything
>> together, with the properties expending into those longhands, and then
>> decide at computed-value time what the actual values of each margin
>> should be, by consulting 'direction' and 'writing-mode' to figure out
>> which '*-source' property to look at, to figure out which '*-value'
>> property to look at.
>
> That solution doesn't, but the solution without the massive
> explosions of shorthands does require separate passes of cascading,
> since the bit about which properties to use is made during the
> cascade.

Ah, okay.  Yes, granted.

(Though if the explosion of longhands is kept internal, as you suggest
in that email, it's not so bad.)

~TJ
Received on Thursday, 9 May 2013 23:41:22 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 9 May 2013 23:41:22 UTC