- From: Sylvain Galineau <sylvaing@microsoft.com>
- Date: Wed, 23 May 2012 22:42:49 +0000
- To: Tab Atkins Jr. <jackalmage@gmail.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>
[Tab Atkins Jr.:] > > 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. > Fair. It will always hurt at some level. Though I'd still like to get a concrete idea of what kind of impact we're talking about. Has this been measured already or are we guessing?
Received on Wednesday, 23 May 2012 22:43:52 UTC