phaistonian

Since being tired and busy isn't the proper status to compose a serious post, here is a list of some stupid IE bugs that kept me busy over the week (such posts require minimum effort and time).

Hopefully the time I wasted trying to figure out workarounds for those ugly bugs will be helpful for others trying to keep up with the IE phenomenon.

1. Never use doctype declaration when writing html to iFrame documents.
   IE will mishandle some events and/or will behave wrong in certain cases (e.g when resizing iFrame.window)
2. Avoid adding comments before declaring a doctype to a document.
   IE will make you mad when handling window related events cause of those comment nodes.
3. When dealing with iFrame documents, use document.body as scope (just for IE) when attaching events, rather than document itself, or you will end up wondering where have your RAM has gone soon enough (memory leaks parade).
4. On IE < 6SP2 referencing window and document through indirectly will RANDOMLY cause problems, so in such cases do it the direct way.
5. To force browser "de-cache" a .js document, make sure the appended string has a .js extension, otherwise IE < 6SP2 MAY cause problems (content type handling issues).

Those all I can recall at the moment.If I had an IE bug log running, I am sure this list would have been way more populated.

IE has been a pretty buggy buddy for many years. A great deal of hours are wasted to keep this "friendship" alive, but honestly, no matter how innovative this browser has been, I am getting to old to keep dealing with this mess.

Hopefully IE8 will have some mercy for our sanity just by following the standards (it sounds easy, does it not?)