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

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

From: Ojan Vafai <ojan@chromium.org>
Date: Wed, 23 May 2012 13:55:57 -0700
Message-ID: <CANMdWTtGM+X7v9zg4-4fNUFf_3fuS0G8_s+=JH_b_Db5_-H44Q@mail.gmail.com>
To: "Tab Atkins Jr." <jackalmage@gmail.com>
Cc: Sylvain Galineau <sylvaing@microsoft.com>, 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:54 PM, Tab Atkins Jr. <jackalmage@gmail.com>wrote:

> 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.
>

Correct.
Received on Wednesday, 23 May 2012 20:56:47 GMT

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