Board Thread:Support Requests - Getting Technical/@comment-27942689-20170328050350/@comment-126761-20170329164036

It looks like it was due to a 'bad' character at the very end of the custom JS, which I've removed. The VisualEditor now appears to load normally!

We've run into this before with a browser extension incorrectly adding a space character at the end of JS pages (Grammarly, I believe) - could that have caused this?