Standards compliance needs to be built into RFP's from the get-go and then enforced by companies who pay the web-dev's.

 
Exactly. I was actually thinking the other day, browsers should be more like compilers... they should refuse to parse incorrect code. Then the enforcement would be on the output end, too.

An example of bad code: http://web1temp.cheme.cornell.edu/courses/cheme112/

Whoever made that site is basically having their bad code justified by browsers that actually display it, even though it has no doctype, no html tag, no head tag, unclosed p tags... etc etc etc. If that person was doi
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************

Reply via email to