>>IOW, they may try to do this just to show that it won't work - but that doesn't mean they should give up. For once they are trying to do it right, and I really don't care if its for all the wrong reasons. They should still do it, bite the bullet and endure the storm - they've started that storm anyway.
>
>Oh no doubt there will be problems, but it's gotta be done. As it stands right now 90% of the problems with JavaScript/DOM related issues are due to Microsoft's quirky rendering. I was just crudely reminded of that as I updated my photo album using jQUery and a few plug ins. Runs perfect in every browser (even several unsupported browsers) except IE. Turns out IE works if certain styles are set explicitly (like a background color in a DIV tag which is just crazy).

The only thing that comes to mind is "I'm crazy only when the south wind blows".

Makes you wonder, is this a case of a rusty ship (http://www.ndragan.com/pv/captain.html)? How stable can it be if it reacts to a certain set of clauses in a DIV... what else may it react to? What other quirks can it have?

>Microsoft deserves all the pain that's directed their way, but now it really doesn't matter what was done in the past. The key is to go forward and produce a compliant browser so moving forward tools can rely on reasonably consistent browser behavior across any browsers.
>
>But we all have to realize that there's going to be pain for a while until the transition has gone through.

As long as Microsoft gets its share. I know I had mine...