Bug Tracker

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#8778 closed enhancement (duplicate)

siblingCheck causes unresponsive script message

Reported by: mike.malamud@… Owned by: mike.malamud@…
Priority: high Milestone: 1.next
Component: traversing Version: 1.5.2
Keywords: ie8 Cc:
Blocked by: Blocking:


In IE8 when there a lot of siblings, the while loop within causes the unresponsive script message.

I am seeing this when it is called from within sortOrder.

Since IE8 does not support compareDocumentPosition, sortOrder is defined to make calls to siblingCheck

sortOrder appears to have been rewritten in 1.4.3 and prior to this, there was no problem.

Change History (10)

comment:1 Changed 12 years ago by Rick Waldron

Component: unfiledtraversing
Keywords: ie8 added
Owner: set to mike.malamud@…
Status: newpending

Thanks for taking the time to contribute to the jQuery project! Please provide a reduced jsFiddle test case to help us assess your ticket!

Additionally, test against the jQuery 0 GIT version to ensure the issue still exists.

In the case of performance issues, we recommend creating a perf test at http://jsperf.com (be sure to use http://code.jquery.com/jquery-git.js & jQuery.noConflict() to test against the most recent jQuery ).

comment:2 Changed 12 years ago by anonymous

Here is a jsFiddle:


This must be run in IE8 and you must make sure that the following registry setting is either not set or not set to some high value that will allow scripts to run forever.

HKEY_CURRENT_USER\Software\Microsoft\Internet Explorer\Styles\MaxScriptStatements

comment:3 Changed 12 years ago by trac-o-bot

Resolution: invalid
Status: pendingclosed

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!

comment:4 Changed 12 years ago by mike.malamud@…

This issue should not be closed. It is a valid issue.

I have a provided a jsFiddle that reproduces the bug.

Please reopen this bug.


comment:5 Changed 12 years ago by nickdk@…

I've also encountered this bug, the jsFiddle Mike provided exactly describes the issue, should be reopened.

comment:6 Changed 12 years ago by Timmy Willison

Priority: undecidedhigh
Resolution: invalid
Status: closedreopened
Type: bugenhancement

Confirmed. http://jsfiddle.net/timmywil/shMjN/11/ The ticket automatically closed and we missed your comment because you posted as anonymous when it was assigned to mike. No worries tho.

comment:7 Changed 12 years ago by Timmy Willison

Status: reopenedopen

comment:8 Changed 12 years ago by cmcnulty

Version 0, edited 12 years ago by cmcnulty (next)

comment:9 Changed 12 years ago by john

Resolution: duplicate
Status: openclosed

comment:10 Changed 12 years ago by john

Duplicate of #7341.

Note: See TracTickets for help on using tickets.