Search about 'flex-basis: auto' in Github https://github.com/search?utf8=%E2%9C%93&q=%22flex-basis%3A+auto%22&type=Code&ref=searchresults

Thanks -- so, those are all candidates that *might* be (but aren't necessarily) broken by bug 1032922. The reason they aren't *necessarily* broken is that "flex-basis:auto" and "flex-basis:main-size" may actually produce the same used value (of "auto"), if the main-size property's computed value is "auto". In particular, if an element has width:auto; height:auto (the initial values), then "flex-basis:main-size" and "flex-basis:auto" are essentially equivalent. (Tab hinted at this in the last sentence of [1].) And in fact, if the author's goal is really "start at the content's auto-width, and then flex from there", then flex-basis:auto is arguably the correct way to express that. (And it's even more correct now that they can directly ask for "auto", instead of having to rely on flex-basis seeing "auto" and then looking over at width to discover "auto" there.) So -- we can't necessarily say anything about the brokenness of the CSS in comment 1, without doing a bit more digging (to discover whether the elements have "width" or "height" set to something non-auto). That sort of thing probably merits its own bug. [1] http://lists.w3.org/Archives/Public/www-style/2014Jul/0008.htm

sorry, [1] was meant to be http://lists.w3.org/Archives/Public/www-style/2014Jul/0008.html (I must've backspaced the final "l" accidentally)