Js Fiddle not loading on Google Chrome

[ghostlyzsh]

I've tried loading jsfiddle on google chrome on a mac and this error shows up:
Uncaught TypeError: e.addEvent is not a function
at t (_dist-editor.js?update_13_05_2019_1:1)
at Object.initialize (_dist-editor.js?update_13_05_2019_1:1)
at Object. (_dist-editor.js?update_13_05_2019_1:1)
at Object.r.extend.$owner (_dist-editor.js?update_13_05_2019_1:1)
at new (_dist-editor.js?update_13_05_2019_1:1)
at HTMLScriptElement.loadEditor ((index):1305)

[oskarkrawczyk]

Tested on newest Chrome on macOS. All working fine.

@ghostlygames is it happening for you when cache is refreshed, on empty fiddle or an existing one?

(closing for now)

[ghostlyzsh]

I think it is a problem with the website. I am opening https://jsfiddle.net/

[oskarkrawczyk]

Can't replicate issue on Chrome. Leaving it as closed.

[James-Livesey]

Getting the same errors too:

_dist-editor.js?update_06_08_2019_1:86051 Uncaught TypeError: el.addEvent is not a function
    at addBound (_dist-editor.js?update_06_08_2019_1:86051)
    at Object.initialize (_dist-editor.js?update_06_08_2019_1:86058)
    at Object.<anonymous> (_dist-editor.js?update_06_08_2019_1:7053)
    at Object.wrapper.extend.$owner (_dist-editor.js?update_06_08_2019_1:1381)
    at new <anonymous> (_dist-editor.js?update_06_08_2019_1:1339)
    at HTMLScriptElement.loadEditor ((index):2035)

Chrome OS 78.0.3904.106 (Official Build) (64-bit) on Chrome (same version number)

[oskarkrawczyk]

Can't replicate. Loads fine on Chrome with no errors.

[James-Livesey]

Strange! It seems quite spontaneous how it works perfectly on some machines but not on others. For me, it hasn't been working for the past few days, and probably not even today (though I haven't checked yet).

…

On Sat, 21 Dec 2019, 17:29 Oskar Krawczyk, ***@***.***> wrote: Can't replicate. Loads fine on Chrome with no errors. [image: Screen Shot 2019-12-21 at 18 28 34] <https://user-images.githubusercontent.com/34213/71311519-c2dbeb00-241f-11ea-89c8-7f7494c0fd6e.png> — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#1458>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKE3S5K3MJ4CZQQLAFO2HCDQZZG6PANCNFSM4HNZHSYQ> .

[oskarkrawczyk]

@James-Livesey Try reloading cache, or disable any content blockers or browser extensions that might interfere.

[James-Livesey]

Yeah tried clearing the cache, still doesn't work. Will test in Incognito to see if it works (without browser extensions interfering)!

…

On Sun, 22 Dec 2019, 14:09 Oskar Krawczyk, ***@***.***> wrote: @James-Livesey <https://github.com/James-Livesey> Try reloading cache, or disable any content blockers or browser extensions that might interfere. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#1458>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AKE3S5MU3NU5LLGZIVVZCRDQZ5YJBANCNFSM4HNZHSYQ> .

[James-Livesey]

Ran it in Incognito, turned out to be a dodgy Tampermonkey script! I should imagine that it could be the same thing for @Ghostly-Coding (just disable each extension until you find a culprit).