Should we push for 1.7.1 before 1.19 is branched?
Version: unspecified
Severity: enhancement
Description
Description
Details
Details
- Reference
- bz32879
| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | None | T31100 Update jQuery version in MediaWiki 1.20 | |||
| Resolved | None | T34879 Upgrade jQuery to 1.7.1 in MW 1.19 |
Event Timeline
Comment Actions
Unless there's a pressing need to stick with the old version yes; new one's faster and has bug fixes, and doesn't appear to drop support for anything we care about.
Comment Actions
(In reply to comment #1)
Unless there's a pressing need to stick with the old version yes; new one's
faster and has bug fixes, and doesn't appear to drop support for anything we
care about.
Hopefully prevents us getting bitten by already fixed regressions and such (granted, this isn't a point release update)
Can we get away with doing it as simply, updating in core, running the JS tests we have, and if they passed, we should be ok? Or will it need some more jiggery pokery than that?
Comment Actions
That's most likely sufficient. There could conceivably be something that breaks unexpectedly (a couple things did break on jQuery 1.6, which had bigger changes).