CSS vs Tables
Out of context: Reply #24
- Started
- Last post
- 51 Responses
- sp0
I think an important distinction to make here, in order to better understand both this debate and technologies involved in web design is that XHTML and CSS work correctly. It is the web browsers that do not implement standards correctly.
In reality, the only reason why using DIV and CSS doesn't work is because of poor browser rendering.
Also noteworthy to this debate is the fact that both Tables and DIVs validate XHTML compliant.
The argument has never been using DIVs over Tables because of validation, it is because the schema and standard specification written by the W3C states that Tables are meant for tabular data not layout.
Another important ideology to put aside is that the use of Tables for layout purposes was a bastardized incantation from designers not from the creators of Markup, the Web or standards.
The reason why DIV is the correct way is because it follows the doctrine of web design.
I can design a car with 20 doors which all open different ways, but it's not a correct implementation of the technology.
Mr. mvb makes a very sound point, the important thing is Validation. Code must be well formed and written clearly, concisely and correctly.
I am a major antagonist of Tables for layout purposes, but the underlying importance of web design is validation by means of W3 recomendations.
As long as CSS, XHTML/HTML validate, I really can't argue with how the designer built the site.
[Note: I do however have a problem with designers whom don't want to learn the proper way of designing sites]
Learning how to use DOCTYPE effectively to create valid and correct markup is most important.
This means learning what tags, elements and attributes are now defunct. For example "height" property in some tags no longer exists, nor does "center" tags.
Because separation of style and content is so important to the life of the web, all "layout" centric elements are being expunged from valid markup.
This is why XML is so important. Even if you never use XML technologies in a design, everyone should learn XML for the simple structure and form of the markup.
The problem is, that as long as designers continue to write poorly formed markup and ignore correct, standards compliant code, bad browsers will linger. If you want to get rid of Netscape 4.7 from clients computers, stop designing for it.
Netscape doesn't even support tha browser anymore, why should we?
And, for those who asked for resurces, take a weekend and check out some of these sites:
http://www.alistapart.com
http://www.webstandards.org
http://www.w3schools.com
http://www.w3.org
http://www.meryl.net/css/
http://glish.com/css/It is aslo worth noting, that proper design standards mean more than just web page layout. Fonts and Scalable graphics can be created by proper coding (XML/SVG), communication with software, services, etc are achieved through standards. The power of web standards goes way beyond that of creative web sites.