Last modified: 2011-12-08 23:42:25 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T34879, the corresponding Phabricator task for complete and up-to-date bug report information.
First Last Prev Next    This bug is not in your last search results.
Bug 32879 - Upgrade jQuery to 1.7.1 in MW 1.19
Upgrade jQuery to 1.7.1 in MW 1.19
Status: RESOLVED FIXED
Product: MediaWiki
Classification: Unclassified
JavaScript (Other open bugs)
unspecified
All All
: Unprioritized enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks: 29100
  Show dependency tree / graph
 
Reported: 2011-12-08 20:03 UTC by Sam Reed (reedy)
Modified: 2011-12-08 23:42 UTC (History)
1 user (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Description Sam Reed (reedy) 2011-12-08 20:03:12 UTC 
Should we push for 1.7.1 before 1.19 is branched?
Comment 1 Brion Vibber 2011-12-08 21:53:52 UTC 
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 2 Sam Reed (reedy) 2011-12-08 21:55:49 UTC 
(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 3 Brion Vibber 2011-12-08 23:18:04 UTC 
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).
Comment 4 Sam Reed (reedy) 2011-12-08 23:42:25 UTC 
Quick look and seems ok

r105612
Note You need to log in before you can comment on or make changes to this bug.
First Last Prev Next    This bug is not in your last search results.

Navigation
Links