-
Notifications
You must be signed in to change notification settings - Fork 5.5k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
100% height on body and html breaks document height calculation using off canvas wrap #4474
Comments
Not able to duplicate this. When i add a bg color to the body it gets applied to the whole doc, not just the VH. |
The height: 100%; also breaks StickyFooter in Foundation. |
If you inspect the templates on Foundation site http://foundation.zurb.com/templates/banded.html |
Found something! When you apply a flat colour it is fine but if you apply a gradient like so it does stop at the actual body height:
|
If you adjust the html css to height: auto; this fixes the issue but obviously this could make alterations somewhere else? |
So this means that 100% height on body stays? Is it really needed? Here is current Foundation 5 and Sticky Footer which is not working: Here I added |
I agree with Aetles, the bug is still there as you can see with the gradient background as in previous comment above. Example here http://cdpn.io/Bgkde |
Looking into it, 100% body height was added in 42be957. The comment says A quick test of off-canvas with body height set to "auto" seems to work here: |
Aetles is correct, that adding height auto to html, body in your app.css file will override Foundations height 100% and will correct any issues with the sticky footer. I am working to find a "cleaner" method to correcting this issue. |
I really don't like the way this was implemented. I needed my html and body tag to have it's real height, but as I can debug it by hovering over the tags in inspection mode, I realised that due to some foundation defaults, the behaviour changed. I always tell others, that one of the best thing in Foundation over Bootstrap, that it don't really mess with your work. Sorry for the long comment, but I'm at the point where I have a foundation-reset css, and it really bothers me. |
It's the same problem I noticed before (#5505), but asked me to post on the forum. I do not know why since it is a problem of Foundation. |
I did ask i in the forums but did not get any real answer there, only this which makes no sense:
|
I did make a change to stickyFooter to support Foundations height 100%, http://github.com/coreysyms/foundationStickyFooter You can leave height 100% in or change it to auto, it's your choice. |
Well great for the Sticky Footer, but this is exactly the issue I think. |
I wonder if it's related to the |
But it's weird really, because normally you would set the html to height:100% so that it will always cover the full height of the viewport. |
+1 I see all the behaviour described: the body is even shortest than the main wrapper div (resolved by putting height:auto to it). I'm a bit confused: I see foundation team doesn't support the community so much (I was fighting with dropdown alignement issue just yesterday and discovered the same "mute" feedback by foundation). It's a pity because it was me who sponsored this over bootstrap in my organization! |
Exactly. I don't mean to be mean, I really do love the framework, and since it's OS, I can hardly complain. |
I tried to remove everything I added to fix the problem and just left a min-height:100%; height:auto; on the first page wrapper. |
Had to reset this again... |
Too bad :( I hope they'll do something. |
Also had this problem with a Foundation HTML document and iframe-resizer. The height of the document could not be calculated due to body and html having Removing the height declaration fixed it. |
Will Foundation 6 fix this? |
Foundation 5.1.0 added the following
This breaks document height calculation when off-canvas-wrap menu is opened (i.e. has .move-right or move-left).
Instead of returning document height, it returns the view port's (i.e. window) height.
The text was updated successfully, but these errors were encountered: