>>
>>BTW, does anyone read the code in jQuery and associated add-ons? I read that a lot (while debugging) and guess what, 90% of the browser specific workarounds are IE specific. And I had to write some for myself - things that work perfectly in FF, Chrome and even Konqueror, just fall flat in IE (dunno if IE8 or 9 was the last I tested, before I handed it to the next programmer). Even a simple case where I was retrieving .innerText of a button in javascript, every browser returned the caption, only IE returned .outerHtml - which I can't find anymore, because I had to rewrite the whole section and make it independent of the caption (well, if you rely on displayed text, you're kludging anyway).
>>
>>I haven't found a single comment where they'd say "IE does this right, others are trouble".
>
>True. OTOH most of that stuff is for IE6 -
>SWAG is that more then 80% will disappear if IE6 is dropped.

There's a succinct summary of MS's current woes at http://www.forbes.com/sites/rogerkay/2013/01/02/microsoft-is-fast-turning-into-a-sideshow/ .

Some of the embedded links are enlightening and amusing.