This web site is about Cascading Style Sheets as a means to separate the presentation from the
structural markup of a web site, and it will help you answer some of those frequently asked Questions,
explains some of the Basics of CSS, gives you tips and tricks for tackling
the problems with Netscape 4, offers you a tutorial about
Positioning with CSS (CSS-P, web design
without tables). There is also a page with interesting Links.
This page uses CSS to present the content in the best possible manner. If you can see this
message, then CSS (or JavaScript) is not enabled in your browser, and the page will not appear as the
designer intended.
The only way to absolutely control the font size x-browser and x-platform is to put the text in a graphic. That is not the most elegant or efficient way to take advantage of the web. There is a very good article that shows the difference between print and web.
One of the better known issues with Netscape and CSS is the fact that
NN 4.xx fails to properly inherit styles.
If you declare font-family and color in the BODY-tag*, IE and NN 6 will use this style in all elements like <table>,
<div> and <p>. NN 4.xx will not.
Therefore you have to specifically explain to NN 4.xx what you expect it to render and how:
body, div, p, blockquote, ol, ul, dl, li, dt, dd, td {
font-family : Verdana, Geneva, Arial, Helvetica, sans-serif;
color : #000088;
font-weight : 400;
font-size : 1em;}
Thanks to Jon Parkhurst I learned that IE also has a serious flaw with inheriting styles into tables. It seems that a font-size declaration in the BODY does not inherit into the TABLE, but the font-family declaration does.
Another NN 4.xx issue: If you declare {font-weight: normal;} on an element, descendant <b> and <strong> elements will not be bold, unless you explictly set {font-weight: bold;} or {font-weight: 900;} on them. This means, BODY {font-weight: normal} will suppress <b> and <strong>'s boldness; and this is the reason why it makes sense to set B, STRONG {font-weight: 900} to restore it.
Netscape and IE render fonts in different sizes, and this is another reason for having two style sheets. NN renders usually a bit smaller, and you have to play with the different sizes. Adjacent font-sizes (e.g., 15 and 16px, 13 and 14px) are usually rendered as the same.
You want to give your visitors the possibility to enlarge/minimize the font-size to their liking, and therefore you define your fontsize like:
p {
font-size: 100%; /* slight emphasis */
}
You check in NN4.xx, and to your surprise you'll find the text grows progressively larger on the screen, especially if you use dynamically generated content.
Bob Swanson provided not only the description of this problem - he also found the solution at the Nu Pointers Bug web site: Putting whitespace around the offending tags fixes the "problem".
Instead of
<p>This is some text</p><p>This is more text</p>
you should take care to have whitespace separating the tags:
<p>This is some text</p> <p>This is more text</p>
Length units for fonts are:
Other topics: