But always design the page so that it will work even if CSS is disabled. Some pages do not and are therefore inaccessible to users.
Indeed. Half the point of CSS is to separate the content and logical structure of the document from its graphical design. You should be able to disable CSS entirely and still have a perfectly readable webpage. (Firefox's web developer menu lets you do this nicely.)
Also, misuse of CSS is pretty rampant, such as using bugs or flaws for formatting. That's a bad idea.
Unfortunately, it's often necessary to abuse CSS bugs, thanks to Microsoft. For example, in Internet Explorer, it's impossible to centre a <div> without exploiting a bug (namely, text-align affecting nested box-level elements instead of just inline elements). Browsers that actually have decent CSS support can use margin-left:auto;margin-right:auto.
Why doesn't IE support this? I'm not sure. Possibly the margin-left/right attributes belong to a CSS version that IE doesn't claim to support. That doesn't excuse them, though; just damns them further for stubbornly refusing to upgrade their buggy and insecure web browser. =\
Indeed. Half the point of CSS is to separate the content and logical structure of the document from its graphical design. You should be able to disable CSS entirely and still have a perfectly readable webpage. (Firefox's web developer menu lets you do this nicely.)
Unfortunately, it's often necessary to abuse CSS bugs, thanks to Microsoft. For example, in Internet Explorer, it's impossible to centre a <div> without exploiting a bug (namely, text-align affecting nested box-level elements instead of just inline elements). Browsers that actually have decent CSS support can use margin-left:auto;margin-right:auto.
Why doesn't IE support this? I'm not sure. Possibly the margin-left/right attributes belong to a CSS version that IE doesn't claim to support. That doesn't excuse them, though; just damns them further for stubbornly refusing to upgrade their buggy and insecure web browser. =\