I can currently see a problem where I add a quirks mode doctype for oldIE, that then in turn triggers Firefox’s quirks mode. Or, adding a strict doctype, and having IE 6 and 7 to deal with, though maybe there is a doctype that triggers quirks in IE 7 that doesn’t affect standards compliant browsers?

I say rip the band-aid off right now and get it over with. This is only delaying the day that it happens, not solving the problem.

I will point out that a successful Firefox created those Google dollars (for the Mozilla Corporation), not the other way around. It is a misperception to think that Google had anything to do with the initial creation of Firefox or with the earlier Mozilla Foundation. The Foundation, which owns MoCo, existed without any of those dollars being present and worked on Firefox, with the larger Mozilla community supporting and contributing much of the work because they believed in it, for a long time without Google. Google is hardly the only source of revenue for MoCo as well. It is simply the largest source.

An important point, at least to me.

I see your point about creating a multi-mode, infinite level scenario. It took me a while to take this in.

I suppose my answer to that concern is that there is an issue of sites written for non-standards. They were written in an environment where there was no need to conform to standards other than the proprietary ones imposed by, but supported market-wide via a near-universal market share, IE6.

Now that remained the case for a long time in web years. Microsoft essentially said to developers: here’s the web as a frozen APi, with ActiveX as a bonus! (haha) and developers said, you beauty. We have to remember that Microsoft’s monopoly is not the only reason that IE6 dominated the market. There was no alternative until a viable Firefox turned up on the back of Google’s dollars. Genuine developers had every right to code for IE6 in all it’s evil glory. Should Microsoft abandon those people after what, two years (in their terms) of heading down a standards compliance route? I don’t think that’s all that reasonable.

Therefore the key is that this ‘version targeting’ has to be a one-version-wonder. The idea of the browser vendor market agreeing to a triple+ standards support environment is madness.

MS should come out and say that whenever IE9 comes about, they will revert to a twin-render-mode model. That way those who have refused to update their IE6 code within approximately a 5 year time frame (from first new of IE7 until delivery of IE9) can reasonably be told to get nodded.

There’s a balance issue. Don’t kill IE6-developed sites just yet, but kill IE6 and add great standards support. That’s what they are doing.

The more developers actually see IE6 disappearing from desktops (something that STILL isn’t happening despute IE7’s significant public lifetime), they will start looking forward and the only option these antiquated developers will see is heading down the standards road.

As much as I hate the idea, allowing Microsoft to maintain some ‘face’ to all those developers they conned into loving IE6, whilst gently, slowly moving towards standards, is better than Microsoft sticking their heads in the sand, which they did for many years.