W3C home > Mailing lists > Public > www-style@w3.org > July 2012

Re: [css3-flexbox] miscellaneous comments on Chapter 4. Flex Items

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Thu, 26 Jul 2012 09:12:03 -0700
Message-ID: <CAAWBYDD=HCK8BeLZ9p8UgirwZ5qPrnj4=nx4bFPNL573bY193Q@mail.gmail.com>
To: Brad Kemper <brad.kemper@gmail.com>
Cc: fantasai <fantasai.lists@inkedblade.net>, "Kang-Hao (Kenny) Lu" <kennyluck@csail.mit.edu>, Anton Prowse <prowse@moonhenge.net>, WWW Style <www-style@w3.org>
On Wed, Jul 25, 2012 at 11:59 PM, Brad Kemper <brad.kemper@gmail.com> wrote:
> I find this pretty weird. 'order' can move something around in one
> dimension, and then absolutely positioning it in the other direction gives
> it a completely different placement for the dimension that stayed 'auto'?
> That is completely counterintuitive. Even a 'float:left' in tlr text that
> becomes abspos (with auto positions) still maintains a pretty similar visual
> ordering with its apparent siblings. 'order' can change what the apparent
> siblings are, and I don't think 'position:absolute' should automatically
> change it back.

I don't understand - turning a float into an abspos doesn't maintain
the visual ordering at all.  It maintains the vertical position,
because both types of positioning use the "static" vertical position,
but the horizontal position will often be very different.

> Doesn't 'margin-left' combine with the 'left' property to affect where a
> left edge ends up, even if it is 'left:auto'? So should 'order' affect where
> an absolutely positioned flex box item end up, even if the edge-positioning
> values are all 'auto'.

margin combines with t/r/b/l exactly as much as border and padding do,
because t/r/b/l position the margin box.

Received on Thursday, 26 July 2012 16:13:01 UTC

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