I had experienced the same thing as you did and when I tried it in Chrome incognito mode it worked. Then I cleared my chrome browser Cache and it went away. Could be a cookie problem?
I think that clearing your cache may have been at the same time that the performance issues resolved. I got better results without clearing the cache.
A cookie issue is for one user, one browser. Several users reported issues in parallel with me. And I had issues across devices that do not share the cooks.
With the service being what it is, the team should not focus on a single user's browser things. That's what you do when you get a single issue that no one else has. We are dealing with forum flaws.
Agreed. Also, clearing cookies/cache on iPhones and iPads is an all-or-nothing thing and a real pain so I will no longer do it for E14. The problem has always resolved itself after a few days, and in the last months, within hours given the frequency of server restarts.
I've noticed this occasionally too, but it seems to self-correct fairly quickly now (e.g. with a page refresh). So I wasn't sure if it was a problem at my end or not, but since you've also seen it, looks like it's not just me! I've yet to grab a log, but will do so the next time I see it.
I've seen it where it only appears to affect certain pages. Works ok elsewhere but not for the page you want to respond to even for several hours after several page refreshes. However clearing the browser cache appears to correct it immediately.
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.
