Ethan said

>We will update this ticket with a link to the public roadmap once this is ready.

This ticket has been closed. I haven't been able to find that link. Can you please post it as a comment to make it easy for me to track? Thanks.

Indeed, the new Viewer/Editor may fix the problem, and you don't want to be fixing bugs in the old version.

Brilliant Roland Thijssen! Your workaround fixed the issue for me (using Chrome on Windows). I disabled both spell checking and translation. Many thanks!

I also experienced a big lag while typing. A workaround that seemed to have worked for me to solve tthis is to turn off spelling check and/or page transaltion and/or support for multiple languages in the browser settings.  

The "workaround" suggests splitting a page up to avoid this problem. Is there a way to do this, yet have the whole lot visible in one go for reading but not, necessarily, editing?

I have a large page, with lots of headings, and numerous code macros and links and so on that, over the last few weeks, has become almost impossible to edit, which is a big issue. I've read an article about confluence that mentions using the "section" macro but, as far as I can see, that doesn't look like it will let me edit single sections without editing the whole document in the way that MediaWiki does. For example, if you look at the page on Confluenc in WikiPedia - https://en.wikipedia.org/wiki/Confluence_(software) - each headed section has an "Edit" link next to it where you can edit only that section rather than using the "Edit" tab at the top, which lets you edit the page.

Is this possible, as that could help me?

Hi all,

This is Ethan from the Atlassian Editor Team. As always, thank you for the continuous feedback on performance improvement needs within the Confluence editing experience.

Since our last update, we have continued to gather feedback and review analytics of the performance of all aspects of Confluence. Based on the data we have reviewed we have determined that the View Page experience is the most in need of attention at this point in time.

This is not to imply however that all our capacity is being diverted away from Confluence editor performance work. Atlassian teams are currently working hard to revamp the underlying collaboration service which powers collaborative editing in Confluence. This is expected to yield significant performance improvements, whether you’re editing a page with others or by yourself. This work is currently ongoing and we will roll out these changes to customers in 2022.

Investing in performance is always a top priority for us, and it’s something that we’ll continue to iterate and improve upon. We’ve found having a specific issue (such as this) to track performance tickets is not necessarily a pattern we want to follow unless there is something clearly broken and reproducible. Rather than keep this bug open knowing that this ticket will not be resolved in the near future, we will use our public roadmap to track issues, and keep you updated on our upcoming editor performance work. We will update this ticket with a link to the public roadmap once this is ready. In the meantime, If you have specific performance issues to share with my team and I, feel free to book time in my calendar here → 30 Minute Meeting - Ethan Yew

Thanks all, and stay safe.

Ethan