#8511 closed enhancement (wontfix)
jQuery 1.3 for 11.6?
Reported by: | Owned by: | ||
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | general | Version: | 0.11.5 |
Severity: | normal | Keywords: | performance |
Cc: | ryano@… | Branch: | |
Release Notes: | |||
API Changes: | |||
Internal Changes: |
Description
changeset:7982 updated trunk to jquery 1.3. During performance testing I applied that patch to 11.5, and see a improvement on page load within browsers.
Plugins on trac-hacks wold have to have similar updates to be compatible, but those changes are backwards compatible with jquery 1.2.6.
Attachments (0)
Change History (6)
comment:1 by , 15 years ago
Keywords: | performance added |
---|
comment:2 by , 15 years ago
comment:3 by , 15 years ago
Mmh yes, backward compatibility with plugins…
Isn't there some jQuery compatibility plugin for the 1.2 to 1.3 API changes? I know there was one for a previous upgrade (jQuery 1.1 to 1.2), but maybe the changes for 1.3 were too extensive for that.
If not, then I (reluctantly) agree the change is probably not worth the trouble.
Yet another reason to move on to 0.12 ;-)
comment:4 by , 15 years ago
The changes for 1.3 are here. Yes, for the larger community, waiting on .12 is best. It might be good to start pushing plugin authors to update their plugins for use with 1.3. I don't know all the js in trac, but it seems the major item, possibly only item, is the removal of using '@'. My read on the change is that removing the '@' from selectors will not break compatibility with 1.2.
comment:5 by , 15 years ago
Resolution: | → wontfix |
---|---|
Status: | new → closed |
Summary: | Jquery 1.3 for 11.6? → jQuery 1.3 for 11.6? |
So now that we decided to put more focus on 0.12 (see [Trac-dev] Re: About next versions (0.11.6 and 0.12)), I think such a change for 0.11-stable is not worth the trouble, so 0.11-stable will stay on jQuery 1.2.6.
comment:6 by , 15 years ago
Cc: | added |
---|
-1 for me: as you said: "plugins on trac-hacks wold have to have similar updates to be compatible"
I really don't think we should break compatibility with so many existing plugins for the sake of performance: 0.12 will use JQuery 1.3, and breaking compatibility with a new "major" release is easier to manage and handle. I can't imagine how many PluginIssue would be logged here after such an upgrade.