Kenny Graham wrote:
> 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.
It would be nice, but would only work if -every- browser did it.
Otherwise the general opinion would be "This new 'Standards Compliant'
browser is broken! Luckilly IE still works."
Would it be so nice? Suddenly virtually all legacy web content wouldn't
be parsed. The web would have disappeared :)
I really believe one of the key factors in the growth of the web, and
the unparrelled transformation it's had on the world in the past decade,
has been the fact that browsers are incredibily tolerant of HTML. That
and HTML being a markup language, not a programming language. It's easy
to learn! Albeit harder to learn to do well.
These two things have allowed millions of people to create websites.
Without this uptake we would not have the web we do now - for good or bad.
I'm not defending sloppy markup, but browser tolerance of such has
allowed us to get to where we are now.
Mike
******************************************************
The discussion list for http://webstandardsgroup.org/
See http://webstandardsgroup.org/mail/guidelines.cfm
for some hints on posting to the list & getting help
******************************************************
