Note that there are some explanatory texts on larger screens.

plurals
  1. POwhat are the root causes of css failure in ie9
    text
    copied!<p>we have a complex .net 2.0 app which uses css as intended. for some reason a subset of web pages renders as if there is nothing on the page in ie9. if you set ie9 to "no style", everything that should be there is visible.</p> <p>we are using the correct mime types on the css files. there are no warning or error messages in the developer tools console. these same pages render without a problem with ie7 or ie8. because we use asp client side validation we are unable to verify how these pages look with alternate browsers.</p> <p>we tried removing the css link, no difference. if you use the developer tools and click on one of the "invisible" elements (td for the most part) tools will highlight its location on the page and a check of the css it has inherited looks reasonable.</p> <p>so at this point we are stumped. we have tried validating the html but there are too many issues for the validator to make much progress, mostly related to the pages being tagged as xhtml transitional. that particular setting was done long before i came on board so i have no idea of whether there was any real thought into choosing it or whether it was just a .net 2 default.</p> <p>any suggestions on analysis tools or approaches to solving this type of problem?</p> <p>=== followup ===</p> <p>not sure if its a css issue or not.</p> <p>the page in question was using a frameset with the following pattern (details ommitted)</p> <pre><code>frameset rows="xxx,xxx" frame style="left: 0px; position: absolute; top: 0px" frameset cols="xxx,xxx" frame frame </code></pre> <p>and thru a process of elimination we found that </p> <p>"style="left: 0px; position: absolute; top: 0px"</p> <p>was the cause of the problem. after finding that the individual frames could be loaded by themselves and they would display without a problem, we started attacking the frameset an element at a time and when the style was removed it would work.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload