flexbugs icon indicating copy to clipboard operation
flexbugs copied to clipboard

Wrapped flex children exceed container with limited height

Open evenfrost opened this issue 8 years ago • 3 comments

Here is a Pen demo.

All browsers except Chrome: flex container with limited height and flex-flow: row wrap; cause flex children with long content to overflow its height. It doesn't happen with flex-flow: row nowrap;.

Chrome: flex children don't overflow container's height in both cases.

Workaround: Set height: 100%; for flex children.

I wonder who is right here: Chrome or all other browsers?

evenfrost avatar Jun 29 '17 12:06 evenfrost

Can you open up a browser bug to get clarification on the interoperability issue?

Without knowing the expected behavior and having a workaround for browsers that don't do the expected behavior, there's not much more to do here.

philipwalton avatar Jun 29 '17 18:06 philipwalton

Definitely must have done it in first place, though I just don't know really what right behavior is lol. Was looking for this issue in bug reports of different browsers really hard but failed to discover one. I'll file a bug report and get back soon.

On Thu, Jun 29, 2017, 21:23 Philip Walton [email protected] wrote:

Can you open up a browser bug to get clarification on the interoperability issue?

Without knowing the expected behavior and having a workaround for browsers that don't do the expected behavior, there's not much more to do here.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/philipwalton/flexbugs/issues/229#issuecomment-312053402, or mute the thread https://github.com/notifications/unsubscribe-auth/AC6ghkgZYT7WG_i5pi9y8iVnRV5HMd9mks5sI-uJgaJpZM4OJPWA .

evenfrost avatar Jun 29 '17 19:06 evenfrost

Well, seems it's Chrome who gone wrong here. See this Buzgilla issue for reference.

This spec change was proposed here, BTW: https://lists.w3.org/Archives/Public/www-style/2014Oct/0489.html and we implemented it in bug 1090031 after the change made it into the spec. It seems that maybe Chrome never implemented it, though. Their bug for this is: https://bugs.chromium.org/p/chromium/issues/detail?id=599828

evenfrost avatar Jul 05 '17 21:07 evenfrost