Misbehaving IE8
When testing IE8 Beta 2 a couple of months ago, I noticed how one innocent line would bring poor pal to its knees:
Element.prototype.cloneNode.call();
Go ahead, try it out. It crashes my browser. Does it crash yours? A few days ago, Release Candidate 1 came out. The “magic” expression still crashes my browser… This doesn’t apply to cloneNode only. Most if not all of the Element.prototype methods (as well as some others) fail in the very same way:
Element.prototype.appendChild.call(); Element.prototype.hasChildNodes.call(); document.querySelector.call();
I tried submitting a bug to IE team few times but only kept getting errors in bug tracker. Here’s hoping to a more stable RC2!
Horia Dragomir said:
#This rocks!
It also crashes IE7, but only the first time you try it.
Pete LePage [MSFT] said:
#Hi!
Thanks for pointing this out! I’m one of the product managers on the IE team, and looked into this bug today after seeing it on your blog. We found this bug after we shipped RC, and have fixed it in our internal builds!
Thanks,
PEte
kangax (article author) said:
#Pete, thanks, that’s good to know. I’m still having problems creating tickets though. Do I need some kind of invitation?