Last modified: 2012-12-16 17:43:09 UTC

Wikimedia Bugzilla is closed!

Wikimedia has migrated from Bugzilla to Phabricator. Bug reports should be created and updated in Wikimedia Phabricator instead. Please create an account in Phabricator and add your Bugzilla email address to it.
Wikimedia Bugzilla is read-only. If you try to edit or create any bug report in Bugzilla you will be shown an intentional error message.
In order to access the Phabricator task corresponding to a Bugzilla report, just remove "static-" from its URL.
You could still run searches in Bugzilla or access your list of votes but bug reports will obviously not be up-to-date in Bugzilla.
Bug 6612 - Ajax code refactoring
Ajax code refactoring
Product: MediaWiki
Classification: Unclassified
Interface (Other open bugs)
All All
: Normal enhancement (vote)
: ---
Assigned To: Nobody - You can work on this!
Depends on:
Blocks: 43175
  Show dependency treegraph
Reported: 2006-07-09 23:30 UTC by Felipe Corrêa da Silva Sanches
Modified: 2012-12-16 17:43 UTC (History)
1 user (show)

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

patch that does this refactoring (19.51 KB, patch)
2006-07-09 23:55 UTC, Felipe Corrêa da Silva Sanches

Description Felipe Corrêa da Silva Sanches 2006-07-09 23:30:01 UTC
I've been doing some little refactoring to the current ajax code. Since it is
intended to grow significantly as new features get developed, I decided to
remove the search feature specific portions of code from ajax.js and put it on a
new AjaxSearch.js file.

It is intended to have a new javascript file and config variable for each new
ajax feature developed in order to allow feature-specific control. All of these
variables default to true in order to still allow the use of $wgUseAjax for
global control.

All ajax files should be created at skins/common/ajax directory.
Comment 1 Felipe Corrêa da Silva Sanches 2006-07-09 23:55:20 UTC
Created attachment 2066 [details]
patch that does this refactoring
Comment 2 Felipe Corrêa da Silva Sanches 2006-07-17 06:35:07 UTC
this bug is closely related to bug 6593.
Comment 3 Aryeh Gregor (not reading bugmail, please e-mail directly) 2006-07-17 18:30:32 UTC
It's not a bug, ergo it's an enhancement.  Don't feel too bad if no one with
commit access is willing to look over a 300-line patch to make sure it's
bug-free and useful; it's only to be expected.  I would suggest you try spelling
out the reasons your patch is useful, and then just forget about it and move on
to other things.  There's really not enough manpower around here to allow all
patches to be reviewed, unfortunately.
Comment 4 Aaron Schulz 2008-08-03 19:20:15 UTC
Seems to have been cleaned up already.

Note You need to log in before you can comment on or make changes to this bug.