If a site is designed for a particular browser, coded such that it only displays properly in one (1) or two (2) browsers, that burden/failing falls upon the Website developer, not upon the browser creator. And the site owner should be cognizant of and forceful about inadequate design.
Yes, all browsers should adhere to all standards, but they don't 
. If a developer is too damned lazy [or ignorant] to make the site work in the four (4) or five (5) major browsers, then the site owner is the one (1) who gets hurt.
Adding a disclaimer to the effect that a site only works in {ie|firefox|chrome|opera|safari|add your browser here} is, to my mind, just not being willing to put forth the effort to make it fully functional. Yeah, it's extra work, but that's what developers get paid to do 
. There's most always a workaround that will fit that particular browser's engine 
.
-barney
Sorry. Not on board there. And no, there isn't always a work-around. Sometimes you are forced to have entirely different behaviour for different browsers -- again, IE is the problem here.
One of the core issues is that HTML is a declarative, markup language, and conditional logic is at best completely insane for it. The conditional logic for IE for style sheets is just moronic. Trying to put conditional logic into JavaScript is similarly idiotic. But, you are FORCED to use conditional logic for what would apparently be trivial tasks, e.g. using a transparent PNG as a design element.
Taking that example, transparent PNGs, you end up with an entire world of pain. It's simply insane. Anyone who has ever done any web design knows that the IE filters used to "fix" the problem are voracious in their appetites for CPU. It's extremely easy to create an otherwise simple design that will grind almost any computer to a halt, and will certainly destroy an older computer.
Trying to code for IE is like swimming with a concrete cinderblock chained to your neck, both arms, both legs, and just to add insult to injury, to any other external appendage that you may have.
At some point you simply need to say, "Bugger this. We're not going to support that anymore."
Sure, you *can* support IE... But do you have the time and money to do it? Development costs money. For a primarily developer audience, there's ZERO reason to support IE 6, 7, or 8, and 9 is debatable.
The site there made the right choice to not support IE. Their audience doesn't use IE, so why bother? It's like manufacturing ski jackets for Mexicans.
Now, for general sites aimed at non-developer audiences, that's a different matter... You have to be careful in how you choose which browsers to support.
If you're doing government or corporate work... god... They're often still using IE6... So you're forced to do a massive amount of work so that the people that commissioned the work can see it, even if the audience for the site doesn't use IE6 at all. That's entirely about who's paying the bills...
(IE6 was around for a dog's age, and there are a large number of applications built for it that are still in use.)
Recent Posts
I like it because it's mine. 
