Re: [css3-flexbox] One final round of bikeshedding on property/value names?

fantasai <fantasai.lists@inkedblade.net> writes:

> On 04/19/2012 11:17 AM, Tab Atkins Jr. wrote:
>> On Tue, Apr 17, 2012 at 1:22 PM, Daniel Holbert<dholbert@mozilla.com>  wrote:
>>> I'm not a fan of "display: flex" -- it sounds to me like it's saying
>>> "this element is flexible".  I think we're explicitly trying to avoid
>>> giving that impression. (since it's the _kids_ that are flexible)
>>>
>>> It would also be a little odd / counterintuitive that the "flex"
>>> property would have no effect on an element with "display:flex", in
>>> usual circumstances.
>>>
>>> 'display: flex-group' sounds better to me.
>>
>> I'm not very concerned about people being concerned about
>> "display:flex" indicating the element itself is flexible - "flexbox"
>> has the same concern, and people seem okay with that.
>>
>> However, it is kinda weird that 'flex' doesn't work on an element with
>> "display:flex". ^_^
>>
>> Since "flex-group" received several votes, and it addresses fantasai's
>> and Anton's feedback, I'll switch to that.
>
> There was an earlier proposal for a 'flex-group' property IIRC,
> does this interact all right with that if we decide to add it
> later?

About as "all right" as the 'flex' value and the 'flex' property, I'd
say.

http://www.w3.org/TR/2009/WD-css3-flexbox-20090723/#propdef-box-flex-group

Just like what's being proposed for 'flex', the 'flex-group' property
was meant for the flexbox items, while the value is considered to be
used on their parents.

FWIW, I'm somewhat in favor of 'display:flex'. It's short, and it
doesn't have 'box' in the name. :) All we have to is get used to is the
noun "flex", which refers to a container that holds "flex items".

-- 
---- Morten Stenshorne, developer, Opera Software ASA ----
---- Office: +47 23693206 ---- Cellular: +47 93440112 ----
------------------ http://www.opera.com/ -----------------

Received on Friday, 20 April 2012 08:30:01 UTC