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

Re: [css-align] Meaning of the "legacy" keyword.

From: Javier Fernandez <jfernandez@igalia.com>
Date: Tue, 24 Jun 2014 13:56:16 +0200
Message-ID: <53A96760.4050401@igalia.com>
To: www-style@w3.org
Hi,

On 06/24/2014 12:40 AM, Tab Atkins Jr. wrote:
> On Mon, Jun 23, 2014 at 3:04 PM, Javier Fernandez <jfernandez@igalia.com> wrote:
>>
>> I wonder whether this inheritance applies also when the value of
>> "align-self" is not auto. The specification does not mention that it
>> applies only to "auto" values, so I assume it causes any other value,
>> even the one specified by the user would be overwritten by the parent's
>> legacy value.
> 
> No, it's only passed when 'justify-self' is "auto", as that's the only
> value that looks at 'justify-items'.  This could possible use some
> cleaning-up.
> 

I think the confusion comes from the sentence about "justify-self" in
the prose describing the "legacy" keyword's behavior, not mentioning it
applies only when using "auto" value. That was already explained in the
justify-self section, so it was redundant but with a different wording.
 In my opinion that sentence could be just removed, since as far as I've
understood, "legacy" has nothing to do with the "justify-self" property.

 I assume this because otherwise it would be the regular
>> behavior of the justify-items, which is defining the default value for
>> "justify-self" when using auto.
> 
> I don't understand what you mean here.  The sentence is defining a
> *special* behavior for "justify-self: auto".

Since that was already explained in the "justify-self" section, and
considering "auto" was not mentioned in this case, I thought that it was
a *special* behavior of the "legacy" keyword, affecting also to the way
the "justify-items" value affects to the "justify-self" one; it would be
a way to overwrite it based on the justify-items value of the container.
Now is clear that I misunderstood the sentence.

Regards

--
Javi
Received on Tuesday, 24 June 2014 11:56:55 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:39:22 UTC