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

Re: [css-flexbox] [css-align] unprefixing alignment properties before css-align

From: Julien Chaffraix <jchaffraix@google.com>
Date: Thu, 13 Jun 2013 17:50:49 -0700
Message-ID: <CAC7ek3Rv7d4O18YzthvLXrWE6F1zk+8cQiq4wRW9Dods1jmTww@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Christian Biesinger <cbiesinger@google.com>, www-style list <www-style@w3.org>, Ojan Vafai <ojan@chromium.org>
>> I would like to unprefix and ship flexbox in Chrome, and have a patch
>> ready to do so.
>>
>> But before I do that, I wanted to hear opinions about shipping the
>> align-*/justify-* properties before we implement the full css-align
>> spec. For example, conceivably, web authors will write code like:
>>
>>   * { justify-content: center; }
>>
>> And for now it will only apply to flexbox, but once we implement
>> css-align, it would start applying to all blocks and mess up layouts.
>>
>>
>> Now personally, I think that risk is somewhat low and people can just
>> fix their sites, but does anyone have other opinions on this?
>
> I think it's acceptable, and we're planning to have Alignment finished
> in the near future anyway.

FWIW our concerns were that there seem to be a mismatch between the
stability of Flexbox and Alignment. The Flexbox specification doesn't
depends on Alignment explicitly [1] but from an implementer's
perspective, because they share the same CSS properties, we have to be
careful with unprefixing before Alignment has enough maturity as they
are already exposed to the web.

Julien

[1] The Grid specification does though and that's what prompted us to
evaluate unprefixing these common properties.
Received on Friday, 14 June 2013 00:51:35 UTC

This archive was generated by hypermail 2.3.1 : Friday, 14 June 2013 00:51:36 UTC