-
Notifications
You must be signed in to change notification settings - Fork 496
IE 11 Nested Flex with row wrap does not wrap the contents when there is a table in its heirarchy #179
Comments
Have you discovered a workaround for this issue? |
@philipwalton Thanks for the response. But I have not yet discovered a feasible workaround because the table can be anywhere in the hierarchy. |
I was able to hack this into working by adding |
@Pokechu22 that doesn't appear to work for the example given, can you share how it's working for you? |
Hm, yeah. It doesn't seem to be correct. Here's a codepen. It does improve the appearance, and for the problem I had, it worked, but for the given example it's broken.
It also does look like |
Hello, setting "flex: 1 1 auto;" instead of "flex: 1;" fix the problem. |
I've also encountered this issue on IE11 while working with an outdated enterprise framework that inserts extraneous I have found that In my case, I am not able to target the closest parent
|
Ran into this myself. Solved it by adding to wrapper elements (ugh, I know) to the existing flex parent that have the styles
this will force wrapping for the nested flex even in IE. My personal usecase: https://codepen.io/risker/pen/OBZxpg |
risker's 'wrapper' and "wrapper-inner" class approach to the containers also worked for my situation, which did not involve a table wrapper. My initial problem was that the content item "div"s were rendering on top of each other. One comment elsewhere suggested that IE did not support percent in the "flex: 1 1 25%". So I changed to "px", but still did not wrap. Once I applied the container class attributes with accompanying CSS, things started working. I also added "flex-direction: column;" to the CSS style for content items. I later added back "%", and it does work. So the "wrapper" and "wrapper-inner" is the secret sauce for IE. |
If we have nested flex containers with a table anywhere in its heirarchy the row wrap does not seem to wrap. This is an IE-11 only issue.
http://codepen.io/anon/pen/kkoLdA
The table need not even be the immediate parent. If its present anywhere in the hierarchy we can see this issue.
The text was updated successfully, but these errors were encountered: