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

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

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Tue, 11 May 2010 19:43:06 -0700
Message-ID: <AANLkTil_SQ84fy6aKg4glhlG8Kccg6E-7QwtiFuvB4Ux@mail.gmail.com>
To: Alex Mogilevsky <alexmog@microsoft.com>
Cc: "robert@ocallahan.org" <robert@ocallahan.org>, Adam Del Vecchio <adam.delvecchio@go-techo.com>, "www-style@w3.org" <www-style@w3.org>
On Tue, May 11, 2010 at 7:37 PM, Alex Mogilevsky <alexmog@microsoft.com> wrote:
> -----Original Message-----
>>From: Tab Atkins Jr. [mailto:jackalmage@gmail.com]
>>Sent: Tuesday, May 11, 2010 7:00 PM
>>What's wrong with margin-collapsing?  I like collapsing margins.  We should certainly have control over whether they >collapse or not, but collapsing by default is, I think, the most useful thing to do.
> I am not sure where to start. Let's just say introducing margin collapsing into Flexbox module is not making it closer to Rec.
> I could be wrong of course. If you manage to define it in a simple way that will make it useful and easy to implement, go for it.

Well, like Robert said, the problems that margin-collapsing can cause
are *already* caused by max/min-widths.  So we don't really gain
anything by disallowing it; the algorithm for flex distribution is
going to have to be robust enough to handle it in any case.

Received on Wednesday, 12 May 2010 02:43:58 UTC

This archive was generated by hypermail 2.3.1 : Monday, 2 May 2016 14:38:35 UTC