W3C home > Mailing lists > Public > www-style@w3.org > April 2015

Re: [css-align][css-flexbox] conflicting propdefs for alignment properties

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 14 Apr 2015 15:53:29 -0700
Message-ID: <CAAWBYDC_Qg6vMO2xna2wcy9JautBNEikFtA81qG2UnkCO-0hyw@mail.gmail.com>
To: Javier Fernandez <jfernandez@igalia.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, www-style list <www-style@w3.org>
On Mon, Apr 13, 2015 at 12:55 PM, Javier Fernandez
<jfernandez@igalia.com> wrote:
> However, I found out another case that perhaps needs further explanations:
>
> * Flexbox:
>   - justify-content
>       + initial: flex-start
>   - align-content
>        + initial: stretch
>
> * Alignment
>   - justify-content
>       + initial: auto -> *Computes* to 'stretch' -> *Behaves* like
> 'flex-start'
>   - align-content
>       + initial: auto -> *Computes* to 'stretch' (Behaves as specified)
>
> So, I understand that we want both properties to have the same computed
> value (stretch) for the initial value ('auto') resolution, but we
> achieve the functionality described in Flexbox using different initial
> values with the *behavior* concept.
>
> Is this correct ? Is this enough clear?

Yes, that's correct.

> I assume that once we can get
> rid of the Flexbox's alignment properties and just refer to the
> Alignment this issues will disappear, but I wonder whether other people
> have concerns as well regarding this.

Depends on what you mean by "go away".  The current text in the
Alignment spec will stay, as it's the behavior we want.

~TJ
Received on Tuesday, 14 April 2015 22:54:48 UTC

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