Menu icon Foundation
Body tag not using 100% height

This one is very strange, I am using F5.2.1 and the body element sizes to the size of the window on load and when you scroll and inspect the body has a fixed height??

An example is here: (just inspect body)

http://cdpn.io/lqhkb

If anyone can shed some light on this it would be great, the only findings I have found if you remove the scss/csss it works again?

cssscsshtmlFoundation 5Body

This one is very strange, I am using F5.2.1 and the body element sizes to the size of the window on load and when you scroll and inspect the body has a fixed height??

An example is here: (just inspect body)

http://cdpn.io/lqhkb

If anyone can shed some light on this it would be great, the only findings I have found if you remove the scss/csss it works again?

Winston Hughes about 5 years ago

@Steve Trask — yes, we see what you're talking about in regard to the element. I have a copy of Foundation v5.1.1 and it appears to be doing the same thing. You can see here: http://cdn.rwh.im/foundation/511/index.html

Also, I have a copy of Foundation v5.0.2 which does not do this. You can see here: http://cdn.rwh.im/foundation/502/index.html

Just taking a shot in the dark here… but it seems like maybe when Foundation hit v1 this started to happen?

Is there a chance it could be a missing bracket or something in CSS or the JavaScript that's causing this? Either way, I'm not that great with JavaScript Debugging but I'll see if I can take a stab at it sometime today and report back if I discover anything worth sharing.

Steve Trask about 5 years ago

I think that a fix may have been made for something else that has impacted this and it has gone unnoticed for while, body and html should be getting document height rather than window height? Also I found d this while digging on the subject:

https://github.com/zurb/foundation/issues/4474

Rafi Benkual about 5 years ago

Thanks for the report. This belongs as a GitHub issue. I went ahead and created one https://github.com/zurb/foundation/issues/4732

We'll follow up on it there.