I believe this is a server-side problem, we're still configuring the website security and so there are times when the site will hiccup, like this.
There's also some lacking of caching for scripts, so what can happen, particularly for the text editors, is that you request the javascript from the server, and rather than receiving a nice, reliable cached version, you're redirected to pull it straight from the server, and the server might not respond, and so it may try to fall back on a browser cached version, and it fails, and you may receive a 50x http error, and it doesn't load.
Then, once you clear your browser cache, it pulls the javascript file properly because the server responds, and it loads. You can confirm this behavior from the browser dev tools, typically.
We have a couple of dev' tickets open on this to be fixed /investigated/worked on in the coming month.
I believe this is a server-side problem, we're still configuring the website security and so there are times when the site will hiccup, like this.
There's also some lacking of caching for scripts, so what can happen, particularly for the text editors, is that you request the javascript from the server, and rather than receiving a nice, reliable cached version, you're redirected to pull it straight from the server, and the server might not respond, and so it may try to fall back on a browser cached version, and it fails, and you may receive a 50x http error, and it doesn't load.
Then, once you clear your browser cache, it pulls the javascript file properly because the server responds, and it loads. You can confirm this behavior from the browser dev tools, typically.
We have a couple of dev' tickets open on this to be fixed /investigated/worked on in the coming month.
