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

RE: [css-flexbox] Summary of planned changes to Flexbox Module

From: Adam Del Vecchio <adam.delvecchio@go-techo.com>
Date: Thu, 29 Apr 2010 13:08:13 -0400
To: "Alex Mogilevsky" <alexmog@microsoft.com>, "www-style@w3.org" <www-style@w3.org>
Message-Id: <20100429170816.800354461@mx1.go-techo.com>
I disagree. I think possibly (at least some of) the box-* positions could be somehow combined into a single box: property, however I think incorporating them into display would make the display property do too much.&nbsp;

However, I think display: flexbox; would have been better then display: box.

I understand that I may be completly wrong with the above, I'm only 2 days into the list. Anyway, that's just my $0.02



--
Adam Del Vecchio (Mobile)
President - Techo TechnologyOn 29 Apr 2010 9:10 a.m., Alex Mogilevsky &lt;alexmog@microsoft.com&gt; wrote: 

&gt; -----Original Message-----

&gt; From: www-style-request@w3.org [mailto:www-style-request@w3.org] On

&gt; Sent: Monday, April 19, 2010 3:44 PM

&gt; 

&gt; On Mon, Apr 19, 2010 at 3:18 PM, L. David Baron &lt;dbaron@dbaron.org&gt;

&gt; wrote:

&gt; 

&gt; &gt; On Monday 2010-04-19 14:35 -0700, Tab Atkins Jr. wrote:

&gt; &gt;&gt; Flex-inline and flex-block are based on the block progression

&gt; &gt;&gt; direction and the writing-mode, and map to one of the first four

&gt; &gt;&gt; values.

&gt; &gt;

&gt; &gt; It seems clearer to say they're based on the inline progression

&gt; &gt; direction and the block progression direction.

&gt; 

&gt; Sure.



I actually don’t like at all the idea of using more display values instead of 'box-direction' and 'box-orient'. I really don't see why this is better. It seems generally harder to understand and it makes the most common cases look less elegant. And it does rely on assumption that 'display-inside' exists, and if that doesn’t happen this becomes really complicated.



&gt; &gt;&gt; Display Order

&gt; &gt;&gt; =============

&gt; &gt;&gt;

&gt; &gt;&gt; box-direction is dropped for now. &nbsp;It seems to be clearer to specify

&gt; &gt;&gt; the direction of flow directly in the display value. &nbsp;I don't *think*

&gt; &gt;&gt; that we've lost anything by this.

&gt; &gt;

&gt; &gt; I presume you're also proposing to drop box-orient.

&gt; 

&gt; Yes.  Sorry, I dropped that in my head so long ago I forgot that I needed to

&gt; call it out.  ^_^



I am still in favor of keeping 'display' values minimal, and having 'direction' and 'orient' separate.



&gt; &gt;&gt; box-align has its start/end values renamed to before/after. &nbsp;It was

&gt; &gt;&gt; necessary to change one of these two properties; you can't have start

&gt; &gt;&gt; and end referring to perpendicular directions. &nbsp;I chose box-align to

&gt; &gt;&gt; be changed so that the mapping makes the most sense for the default

&gt; &gt;&gt; values - before/after act like top/bottom by default, and start/end

&gt; &gt;&gt; on box-pack act like left/right by default, just like they would in a

&gt; &gt;&gt; page with normal english text.

&gt; &gt;

&gt; &gt; I think this might cause more confusion than it fixes.



I tend to agree with Tab on this one. It actually should be 'before|after|middle'. 



&gt; Multiple Lines

&gt; ==============

&gt; 

&gt; Changed box-lines to box-wrap, to more accurately describe the mechanics

&gt; behind it, and to map the values more closely to the white-space property,

&gt; which is its closest analog in static flow.

&gt; Values are `normal` and `nowrap`, default of `nowrap`.  (Not sure about

&gt; naming here.)



'box-wrap' is probably better then 'box-lines'. It seems wrong to have a value called 'normal' which is not the default though. It should just be 



	'box-wrap:nowrap|wrap' (default 'nowrap')

 

&gt; &gt;&gt; Added box-clear property, which takes `start` and `end` values.

&gt; &gt;&gt; box-clear forces a linebreak in a flexbox, regardless of the box-wrap

&gt; &gt;&gt; value. &nbsp;`start` pushes the element onto a new line, `end` pushes the

&gt; &gt;&gt; *next* element onto a new line. &nbsp;Ordinary line-wrapping takes place

&gt; &gt;&gt; after box-clearing happens (that is, first we do all the explicit

&gt; &gt;&gt; linebreaking caused by box-clear, then, if box-wrap is normal, we

&gt; &gt;&gt; check if any line is long enough to need wrapping).

&gt; &gt;

&gt; &gt; These feel to me much more similar to *-break-before/after than to

&gt; &gt; clear. &nbsp;I'm a little skeptical of the use of the "clear" name.

&gt; 

&gt; Yeah, the concepts are similar.  It's possible to use a *-break-before/after

&gt; concept instead.  It would just require an appropriate name.  line-break-

&gt; before/after?



'box-break-before' is intuitive enough I think. It can be 'box-line-break-before' too. Or 'box-wrap-before'.



\

&gt; &gt;&gt; What's left

&gt; &gt;&gt; ===========

&gt; &gt;&gt;

&gt; &gt;&gt; There is a pending question concerning what the best directions for

&gt; &gt;&gt; start/end/before/after to map to is, depending on the display value.

&gt; &gt;&gt; Currently, here are my thoughts:

&gt; &gt;&gt;

&gt; &gt;&gt; right: before is top, start is left

&gt; &gt;&gt; down: before is left, start is top

&gt; &gt;&gt; left: before is top, start is right

&gt; &gt;&gt; up: before is left, start is bottom

&gt; &gt;&gt; inline: before and start are equivalent to whatever the writing-mode

&gt; &gt;&gt; says they are

&gt; &gt;&gt; block: like inline, but before and start are swapped

&gt; &gt;

&gt; &gt; I think start/end/before/after should depend on the block and inline

&gt; &gt; progression directions and not the box direction/orientation. &nbsp;(I'm

&gt; &gt; thinking of things like margin-start/end/before/after. &nbsp;Are you

&gt; &gt; thinking about some other use of these names?)

&gt; 

&gt; No, I'm thinking of the same use of the names.  I'd like a physical-direction-

&gt; agnostic name for the directions, though, to make it simpler to talk about.

&gt; The current draft just explicitly talks about both horizontal and vertical every

&gt; time (well, it skips vertical a lot, but it *could* talk about both all the time)

&gt; and then explicitly talks about what to do when box-direction:reverse is

&gt; specified.

&gt; 



I don't think it would make sense to use start/end/before/after in terms of block-progression rather than box orientation. If it was that way, all four would have to apply to both box-align and box-pack, and a change of orientation without a change of alignment would have very different effect from what it does now.
Received on Thursday, 29 April 2010 17:08:54 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:26 GMT