On 10/19/2012 12:03 AM, edA-qa mort-ora-y wrote:
> On 10/18/2012 08:17 PM, Daniel Holbert wrote:
>> Nightly and Chrome Dev Channel, and they work in both. (For the "new"
>> flexbox version, you need to be using a Firefox nightly build and toggle
>> the about:config pref "layout.css.flexbox.enabled")
> Great, I suppose it was just that missing about:config preference which
> prevented my new ones from working. When is it intended to turn this on
> by default?
Probably during this nightly-release-cycle or the next. Subscribe to
to see when it happens.
> I'm actually working with the SocialAPI, so it may be a few
> versions anyway before we release.
Awesome! If you do end up using new-flexbox, please do file bugs if
things work oddly or anything. :)
> In the meantime I'll stick with the old way. Will this old way be
> supported indefinitely,
It depends on what you mean by "supported". I suspect it will still
*work* in Gecko for the indefinite future, but we'll probably care less
and less about fixing bugs in it, as things switch over to the new model.
For now, though, much of Firefox's UI depends on old-flexbox, so we're
not about to disable it. :)
> I'm a bit unclear on the standards, what's replaced what.
I'll try to clarify... Basically: old-flexbox ("display: -moz-box") was
what we used before this was standardized, because we needed something.
It's part of XUL. There was a tentative W3C spec written around 2009
about how it should work (long after it was already implemented in Gecko
& Webkit), but that spec ended up getting scrapped in favor of a
written-from-scratch "new-flexbox". ("display: flex")
They're two distinct layout models, with different
properties/keywords/etc, but they largely address the same use-cases,
and they behave similarly at a high level.