Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>There is nothing wrong with the CSS code that you have shown so far, so repeating it in a style sheet specific for IE will not make any difference at all.</p> <p>Generally you don't need a separate style sheet for IE. There are some rendering bugs in IE that you may have to circumvent, but that can almost always be done by tweaking the current CSS and HTML.</p> <p>To find out what you need to do to make it work in IE, you should try to find the reasons for the differences. Most CSS is exactly the same, so if you don't see the effect in the page it's usually because the element is not where you think it is or doesn't have the size that you think it has. If for example the height of an element is zero, you will obviously not see it's background color.</p> <p>First make sure that the page has a proper <a href="http://www.w3.org/QA/2002/04/valid-dtd-list.html" rel="nofollow noreferrer">doctype</a>, so that it doesn't render in quirks mode. This is important to make it work as close to the standards as possible in IE.</p> <p>Open the error console in Firefox and view the page. It will tell you if you have any errors in the CSS code. There are standards for how to render correct code, but there is no standards for how to handle incorrect code, so if you have any errors you will get widely different results between browsers.</p> <p>The plugin FireBug in Firefox is useful for seeing exactly which styles affect each element in the page, and you can even edit the CSS and see the result immediately. There is a similar tool built into IE 8 called Developer Tools. For IE 7 you can install <a href="http://www.microsoft.com/en-us/download/details.aspx?id=18359" rel="nofollow noreferrer">Developer Toolbar</a> that gives you some of this functionality. Each tool will allow you to select an element in the code and shows you exactly where it is on the page.</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