https://bugzilla.wikimedia.org/show_bug.cgi?id=33837
--- Comment #4 from Krinkle <krinklem...@gmail.com> 2012-09-30 00:34:41 UTC ---
Keeping compatibility with 1.16 and 1.20 with the same code is somewhat crazy
as there is a huge amount of development in between. wg* globals are probably
the least of your worries (localization, dependencies, new APIs, different HTML
markup, ...).
So I'd recommend to branch or tag your script. Keep the old version as-is for <
1.17, and the new version for anything new. Or if you really do only have this
one specific problem and everything still works as-is, it is easily worked
around with a small wrapper like:
var mwConf = window.mw ?
function (key) {
return mw.config.get(key);
} :
function (key) {
return window[key];
};
They will be removed because they haven't been relevant for 4 major versions,
and any script still using them is definitely overdue for a review (if it
hasn't broken already).
Also note that they wouldn't be really "removed". In a way they are already
gone. Toggle $wgLegacyJavaScriptGlobals to enable/disable the compatibility
layer.
If it was just this on itself, it could be kept for a long while, but it is
part of the whole "legacy / 1.17+" deal (ResourceLoader, Vector, jQuery,
WikiEditor etc.). It is a one-time turning point in the history from one era to
another.
--
Configure bugmail: https://bugzilla.wikimedia.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.
You are on the CC list for the bug.
_______________________________________________
Wikibugs-l mailing list
Wikibugs-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikibugs-l
