Logic. If the site works perfectly which it does right now on any
decent broadband computer it was designed for, why change something
because someone here tells us to, if it breaks the site.
Because you don't know what these issues are going to mean in the
future. Remember Netscape 4? If you were missing an ending td, the
entire page would not render. Now, most browsers correct for that, but,
that doesn't mean that will always be so.
Remember you guys are all a minority to the general public, who don't
know or care if the word Transitional or Strict is at the top of a
page as long as it looks and loads right.
They also don't mess around disabling JS, installing Ad Blockers, etc.
generally speaking.
A lot of people install Ad Blockers, or they install a suite that has ad
blocking enabled by default (Kerio/Sunbelt Personal Firewall, Norton
Antispam, McAfee Internet Security Suite, Panda, AVG, etc). Other people
have host files enabled, and those also block ads, or they block certain
ip addresses. Some people have friends like me, who install things like
this to protect their computers from hackers and such.
Over the past year we had 5.5 million page views in IE. 0.5m in FF.
This is why we cater for IE mostly, but the site is FF compatible
also.
There should not be a compatiblity issue with _any_ browser.
And not one complaint from FF users that the doctype is not
100% valid as there are 12 minor inconsistencies in the code! Come
on, the site works as designed.
It works now, for some people. You have no idea what could be coming in
the future. This is the same thing that happened with Microsoft - DOS
had some minor inconsistancies, and Windows was built on it - we all
know how often Microsoft puts out patches.
The only issue we do agree with is the load times can be high, however
not by broadband, which as we say, the site is labelled as being
designed for.
I have broadband, and do a lot of online shopping - my groceries, ebay,
things for my home, etc. If a site doesn't load quickly, and isn't
simple to use, I'm gone - quick, and never to return. I can always
Google for the item I want and find it somewhere else.
There are still a lot of people who don't have broadband, or their
broadband is slow because of where they are. Basically, you are
discriminating against these shoppers. You need to be careful, you
could easily be sued.
What exactly else is there to complain about? We have taken on some
valuable advice here and the site is now CSS W3C validated and a lot
cleaner thanks to the input here.
Passing HTML validation means that you have completed the markup without
errors. I'm sure all this is done serverside, do you have errors in the
serverside coding as well? Things that will work, with "minor
inconsistencies"? How often are you going to have to go back and fix
something because it failed?
Your best bet is to start with a clean page, then start adding things
and validate each time. Right now, you're trying to fix spagetti - you
need to go one stand at a time. Yes, it's going to take longer, but it
will be worth it because your site will be pretty bullet proof in the
future.