Errors tend to be ignored because (a) many tools to create web pages
create broken code, (b) many designers don't care, (c) many designers
test with IE, and stop testing if it works with IE, and (d) IE tries to
recover gracefully from coding errors by guessing what the designer wanted.
Errors tend to be fixed because designers test their wonderful IE-tested
sites with Firefox, Opera, and/or Safari, and scream WHY DON'T THESE
BROWSERS DISPLAY THE PAGE PROPERLY!!! (Of course, these browsers likely
do.)
This may change with IE8, which is supposed to adhere strongly to the
standards. Those who create broken code are in for a shock.
After Microsoft won the browsers war with Netscape, they did very
little development on IE. In what has to be a classic case of the
"Tortoise and the Hare", Microsoft was caught sleeping as open source
developers (like Google) reinvented the web into "web 2.0". The main
"selling feature" of IE was that it could render any page no matter
how badly formatted (in fact you do not even need main tags like
<HTML>, <HEAD> and <BODY>). But it turns out that search engine
spiders (which are effectively "blind people") can extract much more
useful information from a standards-compliant document. The same is
true for companies using document management systems from companies
like OpenText.
You are correct about crappy publishing tools and this is one reason
why many professional web-developers use plain-text based editors like
Aptana Studio (
http://www.aptana.com). In fact, I think it is safe to
say that 80% of non developers use IE for everything while 80% of
developers first use Firefox to test their initial pages then attempt
to shoe-horn-in tweaks for IE. I can only imagine what the developers
at eBay and Amazon need to do in order to satisfy every customer's
demand to use their favorite browser. At the very minimum they need to
test with 6 different browsers as well as all versions of IE.
One final point, there seems to be a new trend taking place where some
employees will have their PCs replaced with (rather than supplemented
with) mobile devices like the BlackBerry. This means that all dual-use
web pages need to be first developed for hand-held devices, then CSS
is applied to mark up the page for use by full-blown PCs. When a page
is rendered on a mobile device the styles are simply discarded. To
test this with Firefox, make sure you have installed the "Web
Developer" plug-in then type CTRL-SHIFT-S to toggle off the styles.
Repeat the same key sequence to toggle them back on. Use FF to try
this at your favorite corporate web site.
Neil Rieck
Kitchener/Waterloo/Cambridge,
Ontario, Canada.
http://www3.sympatico.ca/n.rieck/