Userscript is consistently causing SE's JS to not load properly

[Mego]

It takes 2-3 refreshes in order to comment, vote, or do anything else that relies on SE's JS code. This issue does not exist without the userscript.

[JJ-Atkinson]

I don't see this happening... Did it start with a specific update? Which browser are you using?

[somebody1234]

It's been happening to me for a few months as well, using Chromium 58 at the moment

[RikerW]

Same here, but it doesn't fix itself when I turn off the userscript.

[vihanb]

Must be either innerhtml bork or tamprermonkey bork

[somebody1234]

:| Who is using innerHTML

[somebody1234]

@RikerW Maybe it's caused by SOX then? (if you have it)

[vihanb]

we're using document.head.innerHTML +=, that will invalidate the existing DOM head, so the scripts might not get correctly reloaded

[Mego]

This has been happening to me for months, but it only got consistently bad within the last few weeks. I have no issues when the userscript is turned off. It happens on both lastest chrome and latest Firefox for me.

On Wed, Jun 14, 2017 at 18:15 Vihan ***@***.***> wrote: we're using document.head.innerHTML +=, that will invalidate the existing DOM head, so the scripts might not get correctly reloaded — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#124 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AA0FEIdR7C1g9w2nw3ILnL57RQY5Ksdkks5sEGmZgaJpZM4N5ex3> .

-- Sent from Gmail Mobile

[somebody1234]

@vihanb Oh no who did this I will report to w3c bad practice department :P

[vihanb]

ok with the removing of the innerHTMLs seems to work :D

[somebody1234]

@Mego Can you try now?

[Mego]

@somebody1234 The issue doesn't seem to be happening anymore. Thanks!

[somebody1234]

@Mego I'm not exactly sure about that, I think it happened to me a few times after I fixed it (although it might be another userscript) so you might want to watch out just in case it happens again