-
Notifications
You must be signed in to change notification settings - Fork 768
sticky footer issue with flex-basis #544
Comments
IE10 is not supported by Flex Layout. If this is also an issue with IE11, please provide a StackBlitz/Plunkr minimal reproduction so that we can check this out. There were some rumblings that we may change the |
I created a stackblitz: This is based on on my project but simplified. IE11 is working fine with my current setup. |
okay, I found the issue again. It has to do with Chrome allowing its elements to shrink below 1. So one issue is visisble here: The fix is in the styles.css (in the root) where I define .fxFlex. Using Same on Safari and I assume FF. So I guess my issue is not 100% an IE bug but more a bug that Chrome allows content to shrink beyond the minimal height, illustrater here: When I apply the flex-shrink 0 to header and footer and flex: 1 0 auto to the body, it scrolls normally. |
Hmm, I just create another fork where I got rid of the flex-shrink 0 on the head and footer. It still works for the footer. However (finally found out why :) in Chrome it allows for the squeezing of the body content into the header (like you see in the sxreenshot above). |
Ok then that's to be expected, we'll try to get a fix in for this as soon as we can. |
I hope I am not confusing you :). |
@ThomasBurleson alluded to a fix for this in #481 (comment). I don't think the PR was ever opened, but should be soon. |
This is related to on-going work to improve usages with flex-basis (see issue #438) |
Not related to this Issue, but @mattiLeBlanc be aware, that on many mobile browsers (including Chrome for Android) the |
thanks @mattiLeBlanc for sharing your solution, it works great! |
@ThomasBurleson Thanks to you and the team for your efforts of getting these issues resolved! |
@mattiLeBlanc - Thank you. Note that we are still working/tweaking improvements for fxFlex. And more REALLY COOL things are coming in April. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
Checking my app on IE10-11 uncovered I was see an issue with my sticky footer. It was not sticky, but just say under the content block positioned above:
So I went back to the article written by Philip Walton a couple of years ago, https://philipwalton.com/articles/normalizing-cross-browser-flexbox-bugs/, and implemented his fix.
However, I was a bit puzzled that this fix is still required nowadays.
So I was wondering if we still need to do this:
Only if I add the
flex:1 0 auto
to the content block, will it work fine in Chrome. I am actually overriding fxFlex at this moment.What is the expected behavior?
Header at top, content stretched and footer sticky at the bottom.
What is the current behavior?
In IE10-11 footer is not sticky at bottom. When adding height 100% to
site
, then Chrome will squeeze the content block so that everything will fit. Fix on, break the other and vice versa.The text was updated successfully, but these errors were encountered: