Any way besides making my editor work in IE I've also added a couple nifty options which will let you really see the difference in the performance of whatever browser you test this with. Once the editor loads up (give it like ten seconds in IE8 LoL...) go in to the advanced options (third drop-down select menu from the top) and check both the keypress and mouseover options. If you test Safari you will have to go in to Safari's Advanced options and put a check for "Press tab to highlight each item on a webpage" to get tab to work. You may also have to click a nearby form element and tab in to the editor or otherwise Safari will choose to go elsewhere. Anyway pressing tab and holding it down (except in newer versions of Opera because they removed the on repeating onkeypress when holding tab down) will really show what a browser's JavaScript engine is made out of.
http://www.jabcreations.com/blog/?promp ... 1&sounds=1
Oh and this isn't a critique, I don't care about the design criticisms of my website. This post is more about the pain of dealing with IE.
- Having to run Virtual PC for IE 4, 5.0, 5.5, 6.0, and 7.0 since 8.0 is my real system install.
- DOM Objects and methods not being supported but instead having JScript equivalents.
- JScript equivalents that are not only NOT DOM equivalents but work differently and less effectively!
- Events are the actual (X)HTML attribute names, not the correct DOM names so the "click" event is "onclick" while the "keypress" event is "onkeypress".
In example when applying a CSS (selector) rule I had to do a for loop for IE! Didn't have to do that for any other browser!
There's plenty more to complain about though I'll leave it at that. Thank goodness for JavaScript object detection!
