Board Thread:Technical Updates/@comment-957747-20180605195901/@comment-25239866-20180606074014

452 wrote: Kirkburn wrote: There may be other causes, It seems unlikely to me that there would simultaneously be identical issues with different causes.

It is much more likely that there is a single - as yet unknown to you - cause, to do with which Kaspersky is a merely a catalyst which is triggering the issue for some.

The most interesting part of this issue to me is that it only happens to me while not logged in as 452, but does happens for me as 452 only on pages where my javascript is disabled, such as my global.js page.

This tells me that it's likely to do with your tracking methods, which my javascript sidesteps, but which my adblock simply blocks when my javascript isn't loaded. This also makes the Kaspersky trigger make sense: because Kaspersky likely detects your tracking as malicious, as it rightly should.

In case anyone in unaware: In Aug 2016, Wikia decided that when you press the submit button, before it would actually save the page, it would first contact their tracking server and log the fact that you're pressing the submit button - rather than do the sensible thing and log that on the server as part of the same request. It used to be that if you blocked access to the tracking server, it would just hang for 5 seconds before timing out and submitting the page, but apparently now it just hangs. I can't tell specifically what Wikia changed which has caused this, but it's probably something to do with how they load the tracking script, which they changed recently due to their tracking being rightfully declared illegal in the EU.

I could be wrong, but this certainly smells likely to me.

Edit: Anyone who is experiencing this issue, or just disagrees with this form of tracking, can add this to their global.js page... Except if you can't edit, you can't add it: Open an edit page, open the console, paste this in the console, and you will be able to submit the page you are on.

$(function { /* disabling tracking which is slowing down every page submit */ $("#editform").off("submit").on("submit", function { $(window).unbind('.leaveconfirm'); }) });

Edit: Oh, and even with this added to your global.js, you won't be able to submit the global.js edit page without copy/pasting that into the console, because your global.js doesn't run on the global.js edit page. Oh Thank you very much. Now no need to Switch to IE any more for editing on HTTPS through Edge