Page MenuHomePhabricator

Set $wgLegacyJavaScriptGlobals = false on ptwiki and ptwikibooks
Closed, DeclinedPublic



Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:46 AM
bzimport set Reference to bz70366.
bzimport added a subscriber: Unknown Object (MLST).

I don't want to step on any toes but can I genuinely recommend against this for the time being? If at all possible I would like to not configure this on a per-wiki basis.

There's lots of cross-wiki gadgets, people using global.js (not just people who are active in multiple languages who can be told to adapt their scripts, but also stewards, global sysops, CVN/SWMT patrollers etc.) who's scripts will break.

As a MediaWiki developer I also have to tell you that we have not yet begun the open migration phase for legacy globals. We haven't "told" anyone yet to migrate, so it's not fair to break things now without giving people fair time to update their scripts.

And again, I highly recommend, for technical reasons and user's convenience and productivity, that we do *not* configure this kind of settings on a per-wiki basis.

For the switch of this configuration for Wikimedia in general, refer to: T35837: Set $wgLegacyJavaScriptGlobals = false by default

Who is supposed to CONFIRM a site request if not the community itself?

Dereckson claimed this task.

I close this request as declined as Krinkle has given a very good rationale to harmonize this kind of decision, and we haven't got any counter argument, feedback or use cases.

Restricted Application added a subscriber: Zabe. · View Herald TranscriptApr 8 2021, 9:49 PM