ResourceLoader/Migration guide (users)

< ResourceLoader(Redirected from RL/MGU)
Jump to: navigation, search
shortcut: RL/MGU

Through time the core JavaScript functions and HTML output improves functionality, introduces new methods, deprecates or changes in other aspects. This document intends to highlight the most common problems that need to be fixed.

  • For an overview of what is currently available in ResourceLoader, check out ResourceLoader/Modules.
  • See also ResourceLoader/Legacy JavaScript for a table with replacements for mediawiki.legacy functions (wikibits, ajax.js etc.).
  • Problems with gadgets? Check if it's listed below. If so, ask a sysop to update it on your wiki.
  • You can help with the migration on Wikimedia projects. See the 2011 Resource Walker, which also has useful tools to ease migration.


MediaWiki 1.28[edit]

Gadget type[edit]


Since early 2011, gadgets with styles (both "only styles" and "styles and scripts") had their styles loaded twice. T42284 and address this bug.

What's new[edit]

This bug was addressed by adding support in the Gadgets extension for the ResourceLoader "type" feature. This allows gadget developers to configure how the module should be loaded

  • type=styles: Load module styles via <link rel="stylesheet">. (Loads early, applies styles before skin and page are ready, also works when JavaScript is disabled.)
  • type=general: Load module scripts and/or styles via mw.loader.load(). (Applies styles after the skin and page are ready, right before JS execution, has better caching.)

Gadgets with only styles, default to type=styles. Gadgets with only scripts default to type=general. Gadgets with both scripts and styles currently default to loading twice (just like the bug was fixed). When this happens, a warning is shown in the console that asks the developer to provide the desired type.

Once we've given gadget developers enough time to migrate, we make type=general the default for gadgets with both scripts and styles.

How to migrate[edit]

Gadget "mygadget" styles loaded twice. Migrate to type=general. See

If you're seeing this warning, it means your gadget contains both scripts and styles. Here is what to do:

  1. If the styles in your gadget are there to provide styling for things created by the gadget, add "type=general" to your gadget definition ("MediaWiki:Gadgets-definition").
  2. If the styles in your gadget are there to provide styling for things that are part of the skin or on the page, then the scripts and styles do not belong together in the same gadget. Convert the gadget to two separate gadgets. One gadget that is styles-only, and the other with the scripts. If the scripts gadget also has some styles, be sure to set "type=general" on that one.

As you can see, in most cases the solution is "type=general." And in a few weeks, this will become the default and we will never again load styles twice.

The reason we will do this in a few weeks and not now, is because of point 2 above. Changing these mixed gadgets to type=general now would cause some styles to load too late and cause a "flash of unstyled content".

MediaWiki 1.27[edit]

Legacy default: mediawiki.util[edit]

The $wgPreloadJavaScriptMwUtil option was removed. This option allowed third-party MediaWiki administrators to re-enable the unconditional preload of mediawiki.util by default for all users (for backwards compatibility). It was disabled by default since MediaWiki 1.26, and has been disabled on Wikimedia wikis since 2014. Extensions, skins, gadgets and scripts that use the mediawiki.util module must express a dependency on it.[edit]

The internal Wikimedia domain "" was deprecated sometime mid-2015. The following common paths should be migrated to avoid breakage once the domain is decommissioned (T107430).

  • . Moved back to local domains, alongside /w/index.php and others.
  •*https://:domain/static/current/: Moved to local domain, sharing a hostname-agonistic Varnish cache.
  •*https://:domain/w/*: Specific versions can now be accessed through the regular script path. Wikimedia's multiversion entry point automatically serves the the file from to the wikis' current MediaWiki version. (T99096)
    •* https://:domain/w/skins/*
    •* https://:domain/w/extensions/*
    •* https://:domain/w/resources/*

MediaWiki 1.26[edit]

Legacy gadgets[edit]

Gadgets are now required to use ResourceLoader. For many Gadgets, migrating to ResourceLoader will be as easy as adding [ResourceLoader] to its definition on MediaWiki:Gadgets-definition. If after adding that, the gadget is not working properly, consult the rest of this page to look for functionality that may have been removed since the gadget was last maintained. If you run into any issues or find features that don't work without a clear way of making it work, please reach out to MediaWiki developers and fellow gadget authors on the talk page, via IRC, or on the wikitech-l mailing list.

Global variables are not global[edit]

When ResourceLoader loads a gadget script, it is not executed in global context. This means that local variables you define in the script are actually local, and not assumed to be also global. They are local to the function your code is wrapped in. It's best to modularize your code to avoid using globals, see "Globals" in MediaWiki's JavaScript coding conventions. However, if you need to export a variable to the global scope, you can explicitly assign them as window properties. For example:

// This is a local variable
var foo;
// This is a local function
function bar() {

// This is a global variable (accessible from other scripts, and from legacy event handlers, e.g. onclick="javascript:Quux();"
window.Quux = function( width, height ) {

Code within your gadget can access foo and bar. Code outside the gadget (or code evaluated as separate programs, such as legacy onclick handlers), can only access Quux..

As of August 2015, ResourceLoader debug mode still executes scripts in global scope (phab:T64605), so your code may seem to work fine in debug mode but be broken in regular mode.

Font mw-geshi[edit]

The font-size of <syntaxhighlight> was often too small by default due to a font-family CSS bug. This was fixed in MediaWiki 1.26 (see (phabricator:T28204).

The mw-geshi, source-css, source-javascript and related classes no longer exist. Related code such as the following can be safely removed:

/* Fix <syntaxhighlight> text size. [[Bugzilla:26204]] */ div, div pre,,
pre.source-lua {
    font-family: monospace, Courier !important;

Inline scripts[edit]

To inject JavaScript inline, use ResourceLoader::makeInlineScript() to wrap the JavaScript code in an anonymous function that can access MediaWiki-related objects properly, and OutputPage::addScript() to add the results to the page source for execution.

For example:

$outputPage = RequestContext::getMain()->getOutput();

$js = 'alert("hello world");';
$wrappedJS = ResourceLoader::makeInlineScript($js);

MediaWiki 1.24[edit]

Internet Explorer[edit]

Browser support for Internet Explorer 6 and 7 changed from Grade A to Grade C. This means JavaScript is no longer executed in these browser versions. See Compatibility for details.

MediaWiki 1.20[edit]

New diff styles[edit]

This version introduces a new diff view, greatly improved in clarity especially for whitespace and other small changes and colour-blind users. If your wiki has custom CSS for the diffs, they may be in conflict with the new style (as happened on ptwiki and srwiki). You are recommended to remove the old code (or if still wanted by some users, update it to work with the new layout and create a gadget for it so that users can opt-in to it still).

MediaWiki 1.19[edit]

wikitable style updates[edit]

As of MediaWiki 1.19 a few bugs have been fixed with the wikitable class (see bugzilla:30485 and bugzilla:33434 for more info). If your wiki maintains a legacy synonym of this class (e.g. "prettytable") you need to update its CSS to match the current style in core.

The current style as of 1.19 can be found here. Copy those rules to your wiki and replace "wikitable" with the synonym (example for nl.wikipedia).

If your wiki doesn't keep something like this, then no update is necessary and everything should take care of itself.

File page checkered background[edit]

Checkered background

The checkered background often applied to transparent file namespace pages is now part of the software. Local rules like the following should be removed (because they are redundant, and actually cause an additional unnecessary HTTP request for the image)

/* Put a checker background at the image description page.
   Only visible if the image has transparent background.
#file img {
	background: url("//") repeat;


Trackbacks were removed from MediaWiki core, so any styling targeting #mw_trackbacks can be removed.

MediaWiki 1.18[edit]

Protocol-relative urls[edit]

This change only applies to Wikimedia Foundation wikis.

As of MediaWiki 1.18 there is native support for protocol-relative wiki installations. This means that a wiki could be accessible from both and To make it possible to a share a common cache for as much as possible, we make use of a technique called protocol-relative urls. Although browsers have supports this for ages, script writers generally aren't very familiar with it until fairly recently. Briefly explained, this means that <img src="//" /> when on "" will be automatically expanded by the browser to This is much like (for example) <img src="foobar.jpg" /> or <img src="/w/foobar.jpg" />, which are are automatically expanded to "".

Depending on how the scripts were written this may require some changes to be made to your scripts. If you use the following method to detect whether the script is executed on a certain wiki, this change will break your script:

if ( wgServer === '' ) {
	// Doesn't work anymore!

because wgServer is now "//". For a few years there has been another config variable, called "wgDBname". You should use that instead to differentiate wikis, like:

if ( mw.config.get( 'wgDBname' ) === 'enwiki' ) {
	// English Wikipedia!

If you must use wgServer, then simply change it to:

if ( mw.config.get( 'wgServer' ) === '//' ) {
	// English Wikipedia!

"Enabled by default" (Gadgets extension)[edit]

As of the version of the Gadgets extension at the MW 1.18 branchpoint, there is a new feature that allows a gadget to be opt-out instead of opt-in based. By setting "[default]" (or adding "|default" to an existing section) the gadget will be enabled by default for everybody, unless a user has specifically opted out by unticking the checkbox on Special:Preferences#mw-prefsection-gadgets.

Note that this also loads it for all anonymous users. Gadgets that are only for logged-in users should be additionally restricted by, for example, requiring certain user rights.

See also Extension:Gadgets#Options.


The actual paths have not changed, but getting the path to the API and index.php has become a lot easier. This also makes the code more portable as it has no hardcoded wiki-specific paths.

This is how it used to go in many gadgets.

var foo = 'bar';
var apiUrl = '//' + encodeURIComponent( foo ) + '&baz=quux';

$.ajax( { url: apiUrl, ... } );

Instead use something like one of the following:

// Behold, mw.util.wikiScript!
var foo = 'bar';
var apiUrl = mw.util.wikiScript( 'api' ) + '?foo=' + encodeURIComponent( foo ) + '&baz=quux';

$.ajax( {
	url: apiUrl,
} );

You may also want to use $.param to automatically escape and create things properly in the query string:

// $.param is also awesome. No need for encodeURIComponent that way :)
var foo = 'bar';
var apiUrl = mw.util.wikiScript( 'api' ) + '?' + $.param( {
	foo: foo,
	baz: 'quux'
} );

$.ajax( {
	url: apiUrl,
} );

You can even use the data option of $.ajax, that abstracts away the need to deal with the query string entirely:

// No longer needed to inject the '?' or '&' in the url
$.ajax( {
	url: mw.util.wikiScript( 'api' ),
	data: {
		foo: 'bar',
		baz: 'quux'
	}, ...
} );

MediaWiki 1.17[edit]


See also jQuery

As of 1.17 the jQuery library is loaded by default on all MediaWiki pages. Each MediaWiki release will keep it up to date with the latest version of jQuery. If you used to load jQuery from within your script, (e.g. from, make sure you remove that. If you load jQuery more than once on a page, it overwrites the earlier version. Other scripts break because they may not work with an older version of jQuery.

Also, by overwriting the jQuery object, any plugins that were bound to that object are also lost.

Global identifier "$j" has been deprecated. Use jQuery or $ instead.

Tabs (vector)[edit]

In 1.17 the HTML construction for the navigation tabs has changed from <li><a><span /></a></li> to <li><span><a /></span></li>. The most common situation in which this causes problems is where scripts assume the presence of the span element when, for example, customizing the tab for "Main Page". Before 1.17 this usually meant that wikis had a different implementation for Monobook and one for Vector (or only one for each and the other was distorted).

Please use MediaWiki:Mainpage-nstab or refer to Snippets/Main Page tab for a script that will work in both Vector and Monobook for 1.17.

Adding portlet links[edit]

The legacy function addPortletLink has been rewritten in the mediaWiki JS Utility library as mw.util.addPortletLink. The syntax and argument order is fully backwards compatible. The differences

  • Support for all core skins now
  • Support for simple id-selector as 'nextNode' (see documentation for details).

Some wikis may have re-defined / overwritten the addPortlinkLink function to support a few extra skins. This is no longer needed. The function definition should be removed and calls adjusted to mw.util.addPortletLink.

The legacy version of addPortlinkLink has been preserved as-is in case some edge cases would behave differently (for that reason the addPortlinkLink does not redirect to mw.util.addPortlinkLink)


The legacy array mwCustomEditButtons has been refactored into the mw.toolbar library. The global array still exists in wikibits to avoid fatal errors but is no longer used due to race conditions. Code may run too late when the toolbar already exists. Using mw.toolbar.addButton will work always, even if the toolbar has already been created.

See mw.toolbar Documentation.

Note that mw.toolbar, just like the old mwCustomEditButtons array, are associated with the classic toolbar. The current default wikitext editor is WikiEditor, which has its own API. See Extension:WikiEditor/Toolbar customization for more information.


The legacy functions such as sajax_init_object have been deprecated. Instead, use $.ajax or mw.Api (from the mediawiki.api module).

Client testing[edit]

Checking which browser, platform, layout engine etc. has should now be done with jQuery.client.

  • is_safari, is_chrome etc. are deprecated
  • No need to navigator.userAgent.indexOf("MSIE 6")==-1 etc.

Sysop script[edit]

New in MediaWiki 1.17 is a user groups module that can automatically load scripts and styles from the MediaWiki namespace for a particular user group. For example, if the wiki has MediaWiki:Group-sysop.js, this script is automatically loaded for all users in that group.

This should obsolete customisations wikis may have with regards to loading MediaWiki:Sysop.js with importScript inside Common.js.


If you need certain scripts like jQuery UI's dialog or datepicker, instead of doing something like:

importStylesheetURI( mw.config.get( 'wgExtensionAssetsPath' ) + '/Example/css/jquery-ui-1.7.2.css' );

$.getScript( mw.config.get( 'wgExtensionAssetsPath' ) + '/Example/js/jui.combined.min.js', function () {
} );

Instead use this:

mw.loader.using( ['jquery.ui.dialog', 'jquery.ui.datepicker'], MyTool.init );

Or if you need to delay initialization until document.ready:

mw.loader.using( ['jquery.ui.dialog', 'jquery.ui.datepicker'], function () {
	$( document ).ready( MyTool.init );
} );

Migrating user scripts[edit]

Contrary to importScriptURI, Wikibits.js functions such as importScript() tend to be widespread among user script. Larger wikis may want to implement their own importScript function in MediaWiki:Common.js to make migration simpler. MediaWiki:Common.js is loaded as part of the "site" module which is guaranteed to load before the "user" module.


When a script depends on another module, such as oojs or mediawiki.util, you will need to declare this as a "dependency". This is because modules are loaded on-demand and asynchronously (in consecutive order: all at the same time), so a script needs to make sure a module has been loaded before it can use its methods. On-site modules, like gadgets, have a registry to declare these dependencies. For user scripts, one has to wrap code with mw.loader.using().

While this has been required since 2011, many scripts have continued to work without declaring their dependencies. Scripts may have worked before by accident as long as at least one user script (that used the same methods) did declare their dependencies and happened to load earlier.

With MediaWiki 1.19, page view performance has been optimised to use fewer modules by default. This makes it increasingly more important to declare the dependencies. Otherwise, your script may fail because any of the 1000+ modules you might refer to in your code would not be loaded yet. Loading everything all the time would be much too slow.

The only two base modules that are always present are mediawiki and jquery.

In practice[edit]

Use mw.loader.using() to declare any modules that you need before executing the contents of "function". You can pass multiple modules as an array of strings.

mw.loader.using( ['mediawiki.util', 'oojs', 'jquery.cookie'], function () {

	/* some other script that uses $.cookie */

	/* some other script that uses mw.util and OO.EventEmitter() */

} );

Global wg variables[edit]

As of MediaWiki 1.17, the global config variables are deprecated. Rationale to clear the global namespace, working towards a reality where most of the core libraries will be object oriented as part of the mediaWiki object. Configuration is managed through an instance of mw.Map in mw.config. It is also supporting the behavior of more script executing in their own local/private scope as opposed to the global scope.

Legacy globals will be kept for backwards compatibly, but people should start migrating so that they may removed in a future version of MediaWiki (Bug 33837).

if ( mw.config.exists( 'wgGlobalGroups' ) {
	// do stuff

if ( mw.config.get( 'wgCanonicalSpecialPageName' ) === 'Search' ) {
	// do stuff

// Retrieve multiple variables for concise repeated access
var conf = mw.config.get( [
] );
if ( conf.wgAction === 'view' ) {
	// do stuff

More info: ResourceLoader/Default modules#mediaWiki.config

Ready, onload, hook[edit]

Check JavaScript deprecation overview for "addOnloadHook". Use jQuery( document ).ready( function ); instead, or $( fn ); for short.

New CSS declarations in core[edit]

Headings overflow hidden[edit]

overflow:hidden for any of h1, h2, h3, h4, h5 and/or h6 can be safely removed from stylesheets as this is now part of the core.

Italic redirects[edit]

Links to redirects appear italicized on Special:AllPages, Special:PrefixIndex, Special:Watchlist/edit and in category listings

.watchlistredir {
        font-style: italic;


Per bugzilla:20276, input#wpSummary's width is now set in Vector as well (instead of just Monobook).

UsabilityInitiative no more[edit]

As of 1.17 the functionality developed by the UsabilityInitiative has been extracted to stand-alone extensions. Buttons like "#pt-optin-try" no longer exist. You can enable/disable these functions like other extensions via Special:Preferences.

Scripts and styles doing things like "HideUsabilityOptIn":

#pt-optin-try {
	display: none !important;

should therefore be deleted entirely as the button no longer exists.

Preformatted JS/CSS pages[edit]

It's no longer useful to wrap these pages in /* <pre> */ or // <source lang="javascript"> etc. In newer versions of MediaWiki, these pages are rendered as code automatically (including syntax highlighting when available). See also bug 4801.

Table sorter[edit]

The old table sorter in wikibits.js was removed in favour of jquery.tablesorter.

Variables such as ts_alternate_row_colors, and functions like ts_parseFloat and ts_dateToSortKey no longer exist.

MediaWiki 1.16 and before[edit]


As of 2008, the function importScript is part of MediaWiki. Wikis that have defined this function themselves may remove that. It will automatically use the new function. This also goes for importStylesheet, importStylesheetURI and importScriptURI.

Make sure that before removing such local function though that the function signature is compatible with the core function and that there are no additional locally implemented arguments or features that core doesn't have (or vice versa). When in doubt, either keep it untouched or replace the function body with a compatibility call to the new core functionality (thus re-routing it instead of removing it entirely).


As of 2008, the function addPortletLink is part of MediaWiki. Many wikis and gadgets have created functions like addLink, addLiLink, addlilink etc. these should be removed as they most likely don't support different skins (ie. only Monobook, not Vector or older skins). Be sure to check the syntax as there is no way of knowing the creator of those local functions used the same parameter order.

Note: The global function was deprecated in 2012 and moved to the mediawiki.util module as mw.util.addPortletLink()


As of 2008, the function appendCSS is part of MediaWiki. Wikis that have defined this function themselves may remove that. It will automatically use the new function.

Note: The global function was deprecated in 2012 and moved to the mediawiki.util module as mw.util.addCSS()

HTML bugs in core[edit]

html lang[edit]

This bugfix is obsolete as MediaWiki does this correctly by default. (example)

var htmlE = document.documentElement;
htmlE.setAttribute('lang', mw.config.get('wgUserLanguage'));

CSS declarations new in core[edit]


The .wikitable CSS class is part of MediaWiki. Wikis that previously defined this class in their Common.css should remove it. Do check if the wiki has any customisations that should be retained (e.g. different background-color, or font-size).


The .plainlinks CSS class is part of MediaWiki. Wikis that previously defined this class in their Common.css should remove it.

Many wikis defined this functionality under a different name: .plainlinksneverexpand. Once any usage is replaced with "plainlinks", it may also be removed. (Search with insource:plainliksneverexpand.)


The CSS classes .mw-plusminus-pos, .mw-plusminus-null, and .mw-plusminus-neg are now implemented by MediaWiki.

External URLs[edit]

Icons for protocols like HTTP, IRC, etc. and file types like PDF are now supported by MediaWiki.

Tooltip and accesskeys[edit]

Scripts like ta['pt-userpage'] = new Array('.','My user page'); are ignored. It was deprecated in 2009. The function akeytt() no longer exists. Tooltips and accesskeys are now supported from core. The most common values that wikis used with ta[] are the same that have now been integrated into the core (ie. "." for "my user page"). They can still be modified, if really needed, by sysops in MediaWiki-messages (no need for JavaScript workarounds anymore).

As of MediaWiki 1.19 the global dummy placeholder ta = new Object(); was removed from wikibits.js. Code trying to add members to it will likely emit an exception.

Good practices[edit]

Anything not related to a particular MediaWiki version that should be noted as it is often done in a way that could or must be better.

Avoid document.write()[edit]

Do not use, will cause blank pages; instead, use jQuery to modify the document (adding elements, changing things etc.) and the import functions to load external resources. (importStylesheet, importScript, mw.loader.load, $.getScript).

Example: replace

document.write('<script type="text/javascript" src="'
             + ''
             + '&action=raw&ctype=text/javascript"></script>');


mw.loader.load( '//' );

Event binding[edit]

Binding events and callback functions is very tricky and it is hard to implement it in good cross-browser way that supports all browsers MediaWiki supports too.

As a good practice it is recommended to use jQuery methods for event binding. See the JavaScript deprecation overview on "addHandler" for examples on more info for this.

Encoding and escaping[edit]

When working with regexes, user input and/or urls always encode and escape!


Do not extend native JavaScript constructors with non-standard methods (e.g. String.prototype.foobar, Regex.myMethod, Array.prototype.inArray etc.). Depend on the es5-shim module to preload (in older browsers) standard polyfills for JavaScript 1.8 and ECMAScript 5 methods. See also Annotated ES5 specification and es5-shim.

// This loader() command immediate runs "done" in modern browsers,
// In order browsers it loads es5-shim.js first.
mw.loader.using( 'es5-shim').done( function () {
	console.log( '    bar    '.trim() ); // "bar"
	[ 'a', 'b' ].forEach( function ( val ) {
		/* .. */
	} );
} );

Getting URL parameter values[edit]

Functions like getURLParamValue, getParamVal, getParamValue, etc. are very common across wikis. Some are better than others (i.e. what if a parameter appears twice? (it should return the last one), does it ignore anything after the #tag?). As of 1.17 mw.util.getParamValue is available everywhere and takes these factors into account. Perform a full-text all-namespace search for these function names. If they are widely used perhaps make a note about it in the local village pump. Any site-wide scripts should be updated to use the mw.util function. If there are any serious problems with the local implementation (like not escaping the value for regex), it may be wise to redirect the function:

function getURLParamValue( p, url ) {
	return mw.util.getParamValue( p, url );

Avoid use of !important[edit]

CSS stands for Cascading Style Sheets. Cascading means what comes later overwrites what came earlier. In most cases there is no need to use !important. See the following example:

.my-element { color: blue; }
.my-element { color: green; }

Text inside <strong class="my-element"> will now be green.

Keep gadgets central[edit]

Gadgets that are highly used across wiki (like Gadget-LiveClock.js) should be kept central (ie. Meta-Wiki or The following is a list of gadgets that are centrally stored and

  • made compatible with 1.17
  • work in Monobook and Vector
  • wiki independent (ie. can be loaded on Commons, Wikipedia, Wiktionary or John Doe's Wiki without problems)

Sysops: To update a gadget on your wiki:

  • Check MediaWiki:Gadgets-definition on your wiki and find the gadget in question.
  • The part after the pipe (|) is the scriptname (eg. "UTCLiveClock.js").
  • Go to MediaWiki:Gadget-<scriptname> (eg. MediaWiki:Gadget-UTCLiveClock.js)
  • Remove everything and replace with the code in they grey area below the scriptname in the list. For an example on how this is done, check out LiveClock on Simple Wikipedia.


  • UTCLiveClock
  • contribsrange
  • modrollback
  • QPreview
  • ShortDiff
  • lastdiff Check Snippets/Last revision action
  • HotCat
 * This imports the latest version of HotCat from Commons.
 * HotCat is a gadget to make changes to categories much easier.
 * Full documentation can be found at [[commons:Help:Gadget-HotCat]]
mw.loader.load( '//' );
  • WikiMiniAtlas
 * WikiMiniAtlas is a popup click and drag world map.
 * See [[meta:WikiMiniAtlas]] for more information.
 * Maintainers: [[w:User:Dschwen]]
mw.loader.load( '//' );
  • Navigation Popups (MediaWiki:Gadget-popups.js and MediaWiki:Gadget-popups.css respectively)
mw.loader.load( '//' );
@import url( '//' );

jQuery optimization[edit]

Use API instead of index.php[edit]

XML retrieved by invoking GET and POST methods on index.php is incompatible with HTML 5, which is the default as of 1.16 (and WMF sites since 17th of September, 2012). You should update code to use api.php, JSON format and jQuery.ajax immediately. Use the ResourceLoader modules that do this for you to simplify interactng with the API, including mediawiki.api.

A temporary fix for problems with DOM parsing of XML retrieved via AJAX: For example the method getElementById("foobar") on a XML object from Mozilla's DOMParser stopped to work as before. Replacing the getElementById with $('#foobar', client.responseText).get(0) might work without many other changes to your code. Updating your script to the above mentioned methods is strongly recommended, however.


See also[edit]

Documentation FeaturesResourceLoader/Features · VocabularyResourceLoader/Vocabulary · Migration guide (users)ResourceLoader/Migration guide (users) · Migration guide (developers)ResourceLoader/Migration guide for extension developers · Developing with ResourceLoaderResourceLoader/Developing with ResourceLoader · Core modulesResourceLoader/Modules · Mobile supportResourceLoader/Writing a MobileFrontend friendly ResourceLoader module
Project information Status updatesResourceLoader/status · Version 1 Design SpecificationResourceLoader/Version 1 Design Specification · Version 2 Design SpecificationResourceLoader/Version 2 Design Specification · RequirementsResourceLoader/Requirements
Other JavaScript DeprecationsResourceLoader/Legacy JavaScript