Side navigation
#8561 closed bug (duplicate)
Opened March 18, 2011 01:32PM UTC
Closed March 30, 2011 04:00PM UTC
Last modified May 20, 2011 04:19PM UTC
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: |
Description
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:
anchor.find("input,select,td,textarea");
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 {
form.find("input,select,td,textarea").tooltip();
}
Attachments (0)
Change History (7)
Changed March 20, 2011 03:30AM UTC by comment:1
owner: | → anonymous |
---|---|
status: | new → pending |
Changed March 28, 2011 11:09PM UTC by comment:2
status: | pending → new |
---|
This was introduced in 1.4.3 when use of sourceIndex was dropped.
Changed March 30, 2011 04:00PM UTC by comment:3
resolution: | → duplicate |
---|---|
status: | new → closed |
Changed March 30, 2011 04:14PM UTC by comment:5
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.
Changed April 05, 2011 08:32AM UTC by comment:6
Replying to [comment:2 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.
Changed May 20, 2011 04:19PM UTC by comment:7
Version 1.6.1 fixes this. Thanks!
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.