What is the status of flexbox support?

[incompl]

I see a bunch of code in there, but I'm not sure what it does. Is it usable? Should it be documented?

[notslang]

We have great flexbox support (#188, #192, #115), but no docs to explain it - only test cases

[incompl]

Are you familiar with what the flexbox support does and how it should be
used? Are you able to add it to the docs? I'd love to document it but I'm
only familiar with the latest version of the flexbox spec and it looks like
the code has support for all multiple versions in some way that I don't
quite grok (display: box; being old and display: flex; being new). I'd love
to try to pull this apart and figure it out when I have time, but it seems
like it'd be much easier for someone who was already familiar.

On Wed, Jun 25, 2014 at 10:42 AM, Sean Lang [email protected]
wrote:

We have great flexbox support (#188
#188, #192
#192, #115
#115), but no docs to explain it

• only test cases

—
Reply to this email directly or view it on GitHub
#262 (comment).

[jamesplease]

We have great flexbox support (#188, #192, #115), but no docs to explain it - only test cases

For future visitors, this is not exactly accurate. Flexbox prefixing fails horribly when used with block mixins (#291), and the only workaround in the issues is to disable prefixing altogether for the mixin (#312 (comment)). There's been no progress on this in years, and work on nib as a library has basically stalled altogether (0 commits on the project in 2016 as of May 2016).

tl;dr avoid nib if you're trying to do all of these things at once:

1. support many old browsers
2. incorporate a responsive design
3. use block mixins for your media queries

Given that the project might be 💀, it might be a good idea to look for alternatives or plan to maintain a fork when bugs like this come up.