Anthony

I don't have any objections, I was just raising a note about the performance. If you all feel this is safe, I'd agree this shouldn't be an issue. @humitos brings...

Also, noted in a chat, we'll eventually have a slightly altered version number in package.json, which is primarily informational anyways, though might affect package installation too. This would be a...

Let's just leave the version scheme as it is. It's not important to have this match Node versioning patterns, as we don't release to NPM. It's just updated in package.json...

Yup, I read that. You still seem to be advocating for altering the version for package.json. I'm describing take *no* action for package.json version -- it should match the version...

> Does adding display: -ms-flexbox fix the bug? I did not test this. In theory it might though, IE11 requires a prefix on flex box rules for what support it...

Most recent update seems to have introduced vertical spacing between elements and did not fix the issue with overflow/wrap on the hlist caption: 

Oops, I take that back. It also looks like you didn't rebuild assets yet, only the SASS source was updated. Trying this change manually does not alter the display however....

It would probably make more sense to revisit in 2.0, when we do drop IE11 support. Feel free to add IE11 support if you'd rather aim for a sooner release.

Can you provide examples of before and after this change? It helps more than looking at the style rules.

I like the placement of the footnote better, that makes much more sense :) When I get a chance I can try to replicate the issue. I'll assign myself, but...