JAB_Creations - 11:10 pm on Oct 21, 2010 (gmt 0)

I did not actually want to do too deeply in to the debate on innerHTML since the code on my site is so in-depth and the issues I encountered were well over a year ago. I would love to debate it to a deconstructionist extent however I simply don't have the time to go bug hunting and figure out what I encountered then. All I can say is when you notice things not working in conjunction with content loaded via AJAX there is a reasonable chance that it's an issue with innerHTML. I also can't remember what versions of what browsers. We'll just have to leave that point at a draw. :)

Though I will stick by my statement that it's proprietary. Even if it's being adopted in to a specification of a different language (which makes ABSOLUTELY NO SENSE) it has and will continue to be a property Microsoft method even if it's been implemented in all the other browsers. So it's not part of any finished spec and HTML5 is not a JavaScript/DOM spec because it's an (X)HTML spec. On top of that I have numerous disagreements with the (X)HTML5 spec.

I think 320KB is excessive, most pages only need about one or two images if that. I'm not saying some pages can't make heavy use of multimedia however most pages simply don't need to. Entertainment should be part of my day, not my entire day. ;) Also my decision to support IE6 is a business oriented one as it will be yet another check on my list of things I can and already do support once I get my business running however trust me when I say I can't wait for it to be a thoroughly mute point. ;)

- John