Skip to main content

Bug Tracker

Side navigation

#8778 closed enhancement (duplicate)

Opened April 05, 2011 08:55PM UTC

Closed May 16, 2011 04:18PM UTC

Last modified May 16, 2011 04:18PM UTC

siblingCheck causes unresponsive script message

Reported by: Owned by:
Priority: high Milestone:
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.

Attachments (0)
Change History (10)

Changed April 05, 2011 11:02PM UTC by rwaldron comment:1

component: unfiledtraversing
keywords: → ie8
owner: →
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 (be sure to use & jQuery.noConflict() to test against the most recent jQuery ).

Changed April 06, 2011 07:36PM UTC by anonymous comment:2

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

Changed April 21, 2011 07:53AM UTC by trac-o-bot comment:3

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!

Changed April 21, 2011 02:13PM UTC by comment:4

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.


Changed April 21, 2011 02:20PM UTC by comment:5

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

Changed April 21, 2011 02:30PM UTC by timmywil comment:6

priority: undecidedhigh
resolution: invalid
status: closedreopened
type: bugenhancement

Confirmed. The ticket automatically closed and we missed your comment because you posted as anonymous when it was assigned to mike. No worries tho.

Changed April 21, 2011 02:31PM UTC by timmywil comment:7

status: reopenedopen

Changed May 10, 2011 08:20PM UTC by cmcnulty comment:8

_comment0: Duplicate of []1305227066030899

Duplicate of #7341

Changed May 16, 2011 04:18PM UTC by john comment:9

resolution: → duplicate
status: openclosed

Changed May 16, 2011 04:18PM UTC by john comment:10

Duplicate of #7341.