Garrett W.

"flex-basis value that does not have a unit declared" --vs-- "unitless flex-basis values" Means the exact same thing to me, in fewer words. Being concise is a good thing.

Which one is Chrome and which is Firefox? Also, has this bug been reported to the dev teams of either browser? If so, please link to the bug reports.

You have not provided enough information to determine the cause of your issue. Please update this issue to include all the information outlined in the [reporting guidelines](https://github.com/philipwalton/flexbugs/blob/master/.github/ISSUE_TEMPLATE.md).

are any of those items using `display: flex`?

This repo is not for general CSS help. I recommend you [ask for help on StackOverflow](https://stackoverflow.com/questions/ask) using the "css" tag.

Chrome and Firefox actually got this right. Even though `.items` is a ``, which would normally be a block element and thus have an automatic width of 100%, being a...

I'm telling you it's not a bug. Want proof? [Read Mozilla's flexbox documentation](https://developer.mozilla.org/en-US/docs/Web/CSS/CSS_Flexible_Box_Layout/Basic_Concepts_of_Flexbox#Properties_applied_to_flex_items) - scroll down just a bit and look under the heading "The flex-basis property", where you'll find...

Yes. Interestingly enough, I think I may have stumbled across a bug somewhere as I'm testing this. As soon as I can identify the nature of the bug, I'll post...

First, I'll explain what's happening. You've discovered [Flexbug #15](https://github.com/philipwalton/flexbugs#flexbug-15) -- on `.items` you have a left and right margin of `auto`, but IE is completely ignoring it. In Chrome and...

I think this issue can be closed now.