fix NTP after another CSS flexbox property rename

fix NTP after another CSS flexbox property rename

BUG=130911
TEST=manual

Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=140464

[Dan Beam, 2012-06-04 16:50:53]

I think it might be better to go back to old flex box until the spec has
stabilized. Wdyt?

[tony, 2012-06-04 18:20:05]

Using old flex box for this (ordering and alignment) is fine.  You're not
actually flexing the boxes are you?

Tab says that this was the last batch of renames.

[Dan Beam, 2012-06-04 19:12:12]

On 2012/06/04 18:20:05, tony wrote:
> Using old flex box for this (ordering and alignment) is fine.  You're not
> actually flexing the boxes are you?

if something's display: -webkit-flex; its children are now flexing 1x1 by
default, right?

> Tab says that this was the last batch of renames.

yay!

[Evan Stade, 2012-06-04 22:04:20]

so does this LG or not?

[Dan Beam, 2012-06-05 00:43:31]

finnnnnnnnnne lgtm (but next time we break, we revert to XUL version)