Bug Tracker

Opened 12 years ago

Closed 12 years ago

Last modified 12 years ago

#7715 closed bug (invalid)

Find() function in jquery datepicker refresh is very slow in ie with 1.4.4 jquery version than 1.4.2

Reported by: [email protected] Owned by:
Priority: undecided Milestone: 1.6
Component: unfiled Version: 1.4.4
Keywords: Cc:
Blocked by: Blocking:


Hi, I've changed 1.4.2 to 1.4.4 jquery version, and my datepicker became very slow (find() function takes about 1s) in ie7. Refresh datepicker takes about 3-5 seconds instead 0.5-1 in ie7. Datepicker is more faster with 1.4.2. Version jquery ui is 1.8.6.

Change History (3)

comment:1 Changed 12 years ago by addyosmani

Resolution: invalid
Status: newclosed

Thank you for submitting a ticket to the jQuery Bug Tracker!. As the particular issue you are experiencing is related to a jQuery UI component, it is recommended that you submit your ticket to the jQuery UI bug tracker as they may be able to better assist in resolving the issue you are experiencing. In addition, if you could submit them a test case on http://jsFiddle.net reproducing the issue (here, speed difference) you are experiencing, that would assist greatly.

comment:2 Changed 12 years ago by [email protected]

I disagree with the above reason for closing this ticket, as I have encountered exactly the same issue forcing me to revert to JQuery 1.4.2 from version 1.4.4. The UI Datepicker module is using the "find" function within JQuery itself which appears to run a lot slower than the equivalent function in 1.4.2.

comment:3 Changed 12 years ago by ajpiano

If there are performance issues with .find(), a ticket about the jQuery UI Datepicker is not the right place to hash out those issues, as, once again, this is the bug tracker for jQuery Core. There are a LOT of jQuery plugins that use .find(), that doesn't mean each should have a ticket on the jQuery core bug tracker. If you can, as addyosmani requested, put together a test case that demonstrates the issue and file it on the UI trac, that would be more appropriate.

Note: See TracTickets for help on using tickets.