Bug Tracker

Opened 11 years ago

Closed 11 years ago

Last modified 10 years ago

#8561 closed bug (duplicate)

Very Slow IE Multiple Selector performance on big html page

Reported by: anonymous Owned by: anonymous
Priority: undecided Milestone: 1.next
Component: unfiled Version: 1.5.1
Keywords: Cc:
Blocked by: Blocking:


This occurs on a rather big html page: 150kBytes and more than 700 "input, select, td and textarea" objects. Using IE6 or IE8, the unresponsive-script popup appears. The bug existed in jQuery 1.4.4 too.

Example code slow statement:


Same effect but now fast:

anchor.find("input"); anchor.find("select"); anchor.find("td"); anchor.find("textarea");

"Workaround", actual code:

if ($.browser.msie) {

form.find("input").tooltip(); form.find("select").tooltip(); form.find("td").tooltip(); form.find("textarea").tooltip();

} else {



Change History (7)

comment:1 Changed 11 years ago by addyosmani

Owner: set to anonymous
Status: newpending

Thanks for submitting a ticket to the jQuery Bug Tracker. Could you kindly provide us with a reduced test that reproduces the issues you're experiencing on jsFiddle.net (as per our guidelines)?. This would assist is in further evaluating your bug.

comment:2 Changed 11 years ago by anonymous

Status: pendingnew

This was introduced in 1.4.3 when use of sourceIndex was dropped.

comment:3 Changed 11 years ago by ajpiano

Resolution: duplicate
Status: newclosed

comment:4 Changed 11 years ago by ajpiano

Duplicate of #7341.

comment:5 Changed 11 years ago by dmethvin

For this case your "IE-only" solution works for all browsers, so just use that. Also, consider using event delegation via .delegate() rather than using .tooltip() for all 700 elements.

comment:6 in reply to:  2 ; Changed 11 years ago by anonymous

Replying to anonymous:

This was introduced in 1.4.3 when use of sourceIndex was dropped.

Thanks! I copied the 1.4.2 sourceIndex sorting code to our local jquery 1.5.2 version.

comment:7 in reply to:  6 Changed 10 years ago by anonymous

Version 1.6.1 fixes this. Thanks!

Note: See TracTickets for help on using tickets.