Hi all, couple quick updates on this:
-
We moved the code that calculates the positions of elements for the responsive view from the browser to the server. The net effect is that there should be less load on the editor in terms of memory and CPU usage, but it also introduces a delay while we fetch the updated data from the server. It’s looking like in practice like the delay is longer than we thought it would be for larger apps, and we’re working on something to speed it up, which we should have out in the next 24 hours. It’s still going to be slower than it was before, though, which we hope is a reasonable tradeoff in terms of making the editor overall lighter-weight and less bloated. (Later this year, we plan to phase out the responsive tab altogether in terms of a much better way of controlling the responsive behavior of apps).
-
If you see it rendering incorrectly, wait for a while and see if it fixes itself. The first time you edit a page, or after you’ve made a lot of changes to page, it might be especially slow (for instance, if you copy a big page, the first time you view the copy in the responsive tab, it might take as long as a minute; it should be much faster on subsequent edits). If it doesn’t eventually fix yourself, please report it to us as a bug report, because while we know and are working on the speed, we’re not currently aware of any bugs in the rendering.
-
On a related note, we’re working on using the same technique to move the issue checker from the browser to the server. This should be a huge win in terms of overall editor footprint, since the issue checker is one of the most performance-intensive parts of the app.
Sorry for all the issues, hope that sheds some light into what’s going on