by debugging ur code. it obviously enters into updatetable (cuz console msg) and here is only code can stuck: it is .using callbacks. i did check state of .tablesorter: it was "loading". indefinetely.

u can avoid this problem, if u will not rely on tablesorter. table will not be sortable, but code will not stuck. at start of ur script, add

mw.loader.load('jquery.tablesorter');

then, instead of $(...).tablesorter(), use

if ($.fn.tablesorter) $(...).tablesorter();

Yeah, I understand how you can use the console output to approximate where it got stuck. What I meant to ask was where you look to find the status of tablesorter. Was there a developer tool or did you just make a modified version of the script that keeps outputting the status?

Thanks for the suggested solution. I assume the "$.fn" comes from JQuery? Also, couldn't I do that check with the if statement even if I didn't call "mw.loader.load"? If I am understanding correctly, the only difference is that I would be relying on the "global" loading rather than also attempting to have my script load it.

mw.loader.getStatus(module)

via console, u can see all available methods of any object. just type it (w\o braces), and hit enter. $.fn contains functions, that added to every jquery object. if tablesorter is here, then u can use $().tablesorter().

if there is no sortable table on the page (during loading from the server), then tablesorter most likely will not be loaded. u can force tablesorter loading, by adding to the page (via template or smth) this:

{|class="sortable" style="display:none"
|}

sorter must be loaded at the start of the script, cuz only by this way u can ensure (~90%) that it will be ready when u need it.

Thanks for the info. It isn't clear to me where you are typing this in to the console but there are lots of menus and whatnot so I'll go through them at a later time to see if I can find the feature you are talking about.

That is certainly an interesting suggestion. Though, as we already know, this issue seems to only be with IE11 + global JS. As such, I am personally not so keen on using it to fix a single case; especially since that solution is 100% wiki-specific (i.e. would have to be done on every wiki you want to use the script on). I'll try loading the module at the start of my script, per your earlier suggestion.

Thanks again for the help. It seems your first solution (using mw.loader.load instead of relying on the general script to load it) works perfectly.

---

Hang on. I seem to have made a mistake in my global JS

mw.loader.load("jauery.tablesorter");

jauery will be hard to find.

I see what you are saying. But now I am even more confused. Somehow, it is working even with that bad load call. Furthermore, I cannot figure out how the script importing works. From past experience, I assumed importArticles only imported the most recent approved version; so I switched to using JQuery.getScript. However, I cannot figure out what is going on with the versions. When I use ?oldid=103007, I get a non-working version as expected. Then I try ?oldid=103032 and it still doesn't work. When I try ?oldid=103033 and ?oldid=103034, I get what I would expect for ?oldid=103032. In case you are wondering what the differences are, I made single letter additions to the label for the last radio button. In 103032 it should be "non-local". For 103033 and 103034, it should be "non-locala" and "non-localab" respectively.

cache, probably.

did u try it on the transformers wiki (where script is)? cuz without test mode enabled, u can't get unapproved revision to load.

I did have a window open with the Transformers Legends Wiki in test mode. I just tried it again and now it is behaving as expected. So I guess it was just a cache issue. I guess refreshing the page wasn't enough.

I still find it odd that having that one line makes all the difference; especially since, as you pointed out, I mistyped the module.

---

Edit:

Just did some more testing. It seams to work now even with the approved version. Although, in both cases, sometimes I have to refresh the page for it to happen. Based on the fact that the approved and modified versions act the same, I am guessing that the success of the script is actually due to a change with Wikia's core; not any of the changes we made.

As long as it works, I guess that is fine with me. Thanks for the help either way.

I have given it some time but it doesn't seem to be helping. I think it is something on Wikia's end that just isn't fixable as far as users are concerned.