[thelist] arguments pro css & xhtml / con tables

Christian Heilmann codepo8 at gmail.com
Tue Jun 20 09:20:09 CDT 2006

> time researchin IE bugs, etc. etc. and pulling my hair out trying to
> get a layout to appear the same in every browser we wanted to support,

And that is the big mistake. The idea of forcing a web site to look
exactly the same on every browser (even in a limited range you want to
support) regardless of quality of the browser itself is just wasting
your time. Who checks your site in several browsers? You, other web
developers and some testers. If you deliver a _consistent_ experience
in a browser throughout your site, all is fine. And this experience is
of course connected to the quality and ability of the browser. I am
happy to get unstyled web sites on Netscape 4.x, cause I can use them.
I am also OK with not getting all functionality Firefox, Opera or
Safari allows for on MSIE6. Get some real users to check your site -
you yourself are far too close to the subject to be able to judge the

The first step to learning and using CSS is not reading the specs, it
is letting go of the rigid ideas of web design of the past that -
based on print design - saw the diversity of user agents, resolutions
and display hardware as a limitation instead of an opportunity.

I stand by what I wrote in the past:
CSS is not hard to learn - if you recognise it for what it is

More information about the thelist mailing list