Google chrome is truncating my web site, why?

Has anyone seen the following rendering bug in google chrome:

bug http://community.mediabrowser.tv/uploads/site_1/126/annoying_rendering_bug.jpg

I get it occasionally when I navigate 开发者_StackOverflow中文版to http://www.mediabrowser.tv

What causes it? Is there any workaround?

---

I can't reproduce this right now, but I've seen similar in the past. Generally this happens when the element with the background is not full height.

Be sure you are applying the background to the body (which defaults to height 100%) and that you are not applying styles to the html tag (which would throw off the body rendering).

Try inspecting that white bit when next it happens. You might gain more insight into what's going wrong.

Another possibility is that the page hasn't finished loading the GA code at the bottom. If your script blocks at the end of your page take too long to execute you might see this before the closing html tag is rendered.

Possibly related: Chromium issue 5388

---

omitted close tag...

It is possible that a closing tag was omitted.

---

I'm running Google Chrome as well, on Windows XP and I am not having a problem with the Rendering. Try closing your tab and reopening sometimes it has a caching type of error like most browsers do occasionally.

---

Part of the problem lies in specifying a height for the container while floating elements inside. Parent elements are never to expand to contain floated children. The only thing preventing this from collapsing altogether is the p element inside the last div. I'm not sure Chrome is doing anything wrong though Firefox is different but I don't have time to look at it further right now.

---

This could be the reason, <div style="overflow: auto; height: 400px;"> if you forget adding overflow: auto to your style or somewhere in your stylesheet that truncation happens. IE can accomodate that, but not Chrom and FireFox. Some default height is necessary but not sufficient. W3C validator pass the code without that elaboration since it does not consider the semantic (logical) errors.