Overview: Various render issues can reproducible be observed in the attached test case (also see URL above). Some lines are not shown in WebKit if the links are invoked in the right order. Steps to Reproduce: 0.) Open the URL above 1.) Click on 'first click' 2.) Click on 'second click' Actual Results: After step 0.) The two above mentioned links are shown. After step 1.) The links moved a bit to the bottom. After step 2.) Some text is shown but some parts covered by a white bar. Expected Results: After step 1.) A text called 'not visible' After step 2.) No white bar. Build Date & Platform: * OS X 10.6.2 - Safari version 4.0.3 (6531.9) * OS X 10.6.2 - Safari version 4.0.3 (6531.9, r49764) * OS X 10.6.2 - Chromium version 4.0.223.5 (29394) Additional Information: * Clicking the links the other way around or refocusing the browser window (e.g. by switching the application) fixes the render issues. * Firefox 3.5.3 shows no render issues.
I have a very similar problem as Alexander. I have a <div> with content that gets updated every time a user changes a set of search filters. For instance, <div><span>Filter 1</span><span>Filter 2</span></div>. Each <span> has styles applied (padding, margin, and background color) and renders perfectly onLoad. However, after the content of the <div> is changed dynamically, the <span>s are chopped by white bars that only disappear upon selecting "Inspect Element."
This would benefit from further reduction - there is no way for XMLHttpRequest to be necessary here. It probably just adds a certain timeout.