Oh, did I say that?
Readers of Piper’s Pages will be well aware of my complete disregard for all things Internet Explorer. I completely decided to ignore the piece of %!#! for my home automation interface.
And now here it is, after a day of planning and a few hours of coding, the d@mn thing is falling on its @ss with a simple scrolling tables implementation while… yup, Firefox, Chrome, Safari, Opera all behave like good little school children.
Really, even if IE had a DOM browser I’d be happier. And JS errors that made sense. But here it is, it’s quite adept at deleting a node from the DOM but adding nodes??? Ya, if you can craft a song that adheres to IE’s rhyme and reason I’ll be quite impressed.
And because there’s no DOM browser I have no idea if the stupid things made their appearance elsewhere in the DOM . Ya, I could slap on an ID, do a getElementById() and see what happens, but then what? The results will just drive me even more crazy.
I have a son now. I don’t have time for this @#!^.
Deryk Piper's Blog 
Just wanted to say… you know, as a developer there’s a difference between a laborious process and a pointless process. If you’ve got a great idea but it’s going to take a lot of work to get it done, that’s a laborious process. If you’ve got a great idea but it’s just not going to work (which is rare) – that’s a pointless process.
Quite often I think of webby things I’d like to implement, and I sit on it for a while because it’s a laborious process to get it done. But at least there’s a light at the end of the tunnel. That light is your reward for a job well done.
Just recently I did some work on my Home Automation interface, attempting to bring “compatibility scrolling” in line with the native scrolling that was developed with Firefox in mind. The whole scrolling-tables thing has been a long time in development, but today I was finally able to get Chrome and Safari (ie, Webkit) going along with Firefox. At one point it looked like I’d have two divergent paths, but there it is that we’re in the right place. And as a bonus, compatibility scrolling works in Firefox as well (with one little caveat, which I’m sure I’ll fix soon enough).
So – follow the rules, and the rules reward you. That’s in stark contrast to this cr@p with IE, which can quite easily turn any laborious process into a pointless process. Who wants to spend the time cooking up some tasty web dish, and make it work in IE, when IE is going to make you jump through arbitrary hoops to get there?
Boo IE. Booooo.
IE has redeemed itself. Barely.
It turns out that, in this instance, IE was being more strict than its counterparts. This doesn’t absolve it of all its sins however – the whole reason for going on this charade was to code around IE’s refusal to recognize code that the 3 other major rendering engines have no problem with.
So score one to IE. But when you’re down by about 1,000,000, does one point really matter?