siblingCheck causes unresponsive script message

[mike.malamud@…]

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.

[Rick Waldron]

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 ).

[anonymous]

Here is a jsFiddle:

​http://jsfiddle.net/thecountofzero/shMjN/7/

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

[trac-o-bot]

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!

[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.

Thanks.

[nickdk@…]

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

[Timmy Willison]

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.

[cmcnulty]

Duplicate of #7341

[john]

Duplicate of #7341.