Home Dashboard Directory Help
Search

javascript dom methods running slow by JeffreyHWright


Status: 

Active


Type: Bug
ID: 804393
Opened: 10/2/2013 9:18:18 PM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

I haven't tested any beyond these two, but it seems that the removeChild and appendChild functions are running about 10x slower in ie11 than in Chrome. I've tried on two different machines and get similar results. I put the test I created on jsfiddle.

http://jsfiddle.net/repNU/5/

Details
Sign in to post a comment.
Posted by Microsoft on 10/10/2013 at 12:03 PM
Thank you so much for the feedback.

Unfortunately, we are not able to address this feedback in our upcoming release. We will consider your feedback for a future release. We will keep this connect feedback bug active to track this request.

Every piece of feedback we receive is important to us and helps us improve the quality of Internet Explorer.
We continue to welcome more feedback, so please don't hesitate to report other ways that we can improve Internet Explorer.

Best regards,
The Internet Explorer Beta Team
Posted by JeffreyHWright on 10/7/2013 at 3:06 PM
I've updated the script to run fewer iterations and is removing and adding less html while still seeing the same timing differences.

http://jsfiddle.net/repNU/7/
Posted by Microsoft on 10/3/2013 at 11:06 AM
Mr Wright,
Great feedback!

Although I'm definitely seeing differences in loading times between browsers, I am also seeing unresponsive script dialogs in IE, Firefox and Chrome. Also, I'm sporadically seeing browser crashing in IE and Firefox. I'm wondering if you were also seeing this behavior? It is not 100% of the time but it is happening enough that any speed comparisons that I run are not valid.

Could you revisit your JSFiddle script and check for scripting issues(ie crashing browsers/unresponsive script messages)?

We are going to investigate your feedback further either way because I do see enough of a difference to warrant more testing. But if the script is somewhat unstable in more than just IE, it will be harder to determine resolution.


Best regards,

Corey Wilson - The Internet Explorer Team
Sign in to post a workaround.