Board Thread:Support Requests - Getting Technical/@comment-5558012-20160808164234/@comment-24473195-20160808235026

Saftzie wrote:One way of adding a "config" option would be to add a query parameter, like "&powerpagemaker=0" after the "?action=edit" query in the URL bar. (This suggestion is hypothetical, not functional, at the moment.) That's not particularly smooth, though.

Anything loaded (like a config) from user JS would be loaded after site JS had already loaded and run. That's fine too. Since user JS is the last to load, all they'd need to do is make the script opt-in instead of default. Although they'd need to use either cookies or local storage for that to work on every page load.

The most recent gadget extension seems to have the exact same problem. There is no concept of global gadgets, and even if gadgets were enabled on all wikis the problem would remain. There would need to be a central wiki for it and they'd also have to handle the name clash between local and global gadgets to make that work. The codeload idea is interesting but also doomed to fail because it isn't deployed globally. Few wikis will care to use it.

One crazy alternative to solve this actual problem would be to make use of a something like tampermonkey (or another tool) to trigger  "?usesitejs=0" on page load then filtering and dynamically loading only specific scripts using a user's javascript.

Wikia might possibly be convinced to do some kind of "vanilla" theme that discards all css, but javascript is considerably more complicated to kill.

Similar question: https://www.mediawiki.org/w/index.php?title=Topic:T401bqgw6uwfg607