Freezing page while editing when using expand macro

[Angelika Wabik]

We have created a new page template for our team that uses several macros as mention, date and status as well as multiple expand macros. Right now one of the pages contains 19 expand macros and some of our teammates are experiencing freezing of the page while editing and the text appearing with delay when writing but it doesn't occur in all team members. This significantly hinders work. Is this problem known to Confluence team?

[Kristian Klima]

Hi @Angelika Wabik 

Too much content can be an issue and the reason why you're experiencing 'jitters'. 

I have a page that's a '409 minute read', it's basically a single giant table and editing it borders on impossible (we're working on changing the approach to this...). Our experience is identical to yours.

If you have 19 expands, each with a considerable amount of content, might be a problem.

Consider reorganizing content across several pages or you inclusion macros.

[Thiago P _Atlassian Support_]

Hey there @Angelika Wabik ,

There is no way to say what is the root cause without checking the page in question and the specific conditions in which they happen. Feel free to open a Support ticket and we'll help to investigate this issue.

On possible causes - the macros you mentioned are not known for causing performance issues, but if the page in question has large tables, this may be triggering CONFCLOUD-81975

The specific conditions for this Bug are:

1. page uses the new Cloud editor (aka. Fabric)
2. has at least one large table, or multiple tables

Our Development Team is actively investigating this Bug, but for now reverting affected pages to the Legacy editor is one of the options. Breaking up large pages into smaller ones, or moving large tables to Databases / Excel files are also valid Workarounds.

Hope this helps!

[Dan Breyen]

Hi @Angelika Wabik welcome to the community.  I took a quick look out on Atlassian's Jira Site and didn't find anything that looked related to your issue. 

Do you know if this is an issue with different browsers?  

If you can replicate the issue and/or have some examples, I would suggest working with Atlassian Support and they can further assist you to determine if this is a known issue or work with you to create a new work item for them to look at.