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

Re: [css3-flexbox] flex-basis initial value should be 0px

From: Tab Atkins Jr. <jackalmage@gmail.com>
Date: Wed, 23 May 2012 13:54:35 -0700
Message-ID: <CAAWBYDC6Z-rJj4oHOFhdzZoq-T4qeiGh032KTfdpn+mAT2gD5Q@mail.gmail.com>
To: Sylvain Galineau <sylvaing@microsoft.com>
Cc: Ojan Vafai <ojan@chromium.org>, Tony Chang <tony@chromium.org>, fantasai <fantasai.lists@inkedblade.net>, "www-style@w3.org" <www-style@w3.org>
On Wed, May 23, 2012 at 1:52 PM, Sylvain Galineau
<sylvaing@microsoft.com> wrote:
> [Ojan Vafai:]
>>This is the part I disagree with. When we break an edge case visually, it's relatively straightforward for a developer
>>to look up the documentation for flexbox (e.g. on MDN) and figure out how to fix it. On the other hand, when the
>>performance is slow, it's almost impossible to gain insight into what's causing it to be slow. As a web developer,
>>you're most likely to throw your hands up and assume the UA just hasn't optimized flexbox, at which point you'll
>>either not use flexbox or live with your site being slow to load, both of which are unacceptable.
> Second layout passes are never fun but are we talking about an impact that will be noticeable to your average
> author building a nav bar? How are they going to notice it i.e. what's the baseline? Would they be able to tell
> the flexbox version is visibly slower than the built-with-divs-and-duct-tape version?

Ojan and Tony are mostly concerned about the speed effect on Flexbox
used for page layout, where the contents of the flex item might be
"the entire body of the page".  The effects on a nav bar are obviously
small enough to probably be completely ignorable.

Received on Wednesday, 23 May 2012 20:55:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 25 March 2022 10:08:16 UTC