- From: Tab Atkins Jr. <jackalmage@gmail.com>
- Date: Thu, 9 Apr 2015 16:32:32 -0700
- To: Christian Biesinger <cbiesinger@google.com>
- Cc: Greg Whitworth <gwhit@microsoft.com>, www-style list <www-style@w3.org>
On Thu, Apr 9, 2015 at 4:30 PM, Christian Biesinger <cbiesinger@google.com> wrote: > On Thu, Apr 9, 2015 at 7:24 PM, Tab Atkins Jr. <jackalmage@gmail.com> wrote: >> On Thu, Apr 9, 2015 at 4:21 PM, Christian Biesinger >> <cbiesinger@google.com> wrote: >>> I see. This is getting really complex. So you expect flexbox >>> implementation to implement this part of css-align for abspos items, >>> even if they don't otherwise implement that spec? >>> >>> This is a lot of code for a not very useful feature. Who puts abspos >>> items in a flexbox and expects them to kinda-sorta participate in flex >>> layout? >> >> They're not participating in flexbox layout, at all. They're just >> participating in Alignment, which *started* in Flexbox, but now >> applies to all display values. > > Yes, but per your response I need to implement alignment for abspos > items inside of flexbox even when I don't otherwise implement > alignment, unless I misunderstood you. If you're implementing the Alignment properties for abspos at all, yeah, you should do it properly. It's perfectly okay at the moment to implement them for only *some* layout types; we'd prefer they get properly implemented for everything, but that's a good bit of work. If you don't want to do Alignment for abspos *at all* yet, that's fine, but you shouldn't do a partial implementation of abspos alignment. ~TJ
Received on Thursday, 9 April 2015 23:33:19 UTC