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

Re: [css3-flexbox] does flex-order impact stacking order of overlapping content

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Fri, 27 Jan 2012 12:39:22 -0800
Message-ID: <CAAWBYDCaxNF_HTsVJcvkbQUP3ksOkd0pjW-+ALqGn99q8syJUw@mail.gmail.com>
To: Daniel Holbert <dholbert@mozilla.com>
Cc: "www-style@w3.org list" <www-style@w3.org>
On Fri, Jan 27, 2012 at 12:04 PM, Daniel Holbert <dholbert@mozilla.com> wrote:
> Hi www-style,
>
> In the current Flexbox ED "Layout Algorithm" section, it says this about
> flex-order:
>
>> Re-order the flexbox items according to their ‘flex-order’.
> [...]
>> This affects the order in which the flexbox items generate
>> boxes in the box-tree
>
> Given that -- hypothetically, if two flexbox items were to contain
> overlapping content[1], would flex-order have any effect on which one
> overlaps the other? (i.e. does flex-order affect stacking in the z axis?)
>
> I've been assuming "no", since (discounting the "z-index" property) elements
> generally stack in the z axis according to *document order*. So, since
> flex-order is independent of document order, I wouldn't expect it to affect
> stacking in the z axis.
>
> Just wanted to clarify, though, because "the order in which flexbox items
> generate boxes in the box tree" sounded like it might impact stacking-order.
>
> Thanks,
> ~Daniel
>
> [1] I'm not 100% sure that it's even possible to get overlapping content in
> different flexbox-items, but I'm guessing it might be doable with
> "position:relative" or something.

I'll wait for Alex to find a previous decision, but I could go either
way, depending on whether we want to think of flex-order as
manipulating the box-tree or not.

~TJ
Received on Friday, 27 January 2012 20:40:10 GMT

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