Performance issue input text

[ArthurP]

Hi,

I have some performance issue when modifying a document in webauthor. There is a lag at the character input, making it hard to write.
I'm not sure how to investigate it. In the browser console, I see that "insertText" action is taking time to performe.

I have a custom framework with custom javascript actions and CSS.
To investigate,

• I disabled all the custom CSS, nothing changed.

• I disabled all the javascript actions, it was better

• I started adding javascript actions one by one, when two of them extend "sync.actions.AbstractAction", lag started again. When there is only one action it's ok. If I accept all tracking changes, lag disapear.

Can you provide some guidance on how to investigate and if you are aware of some performance issue with tracking change ?

Thanks

[cosminef]

Hello Arthur,

Thank you for reaching out.
Could you please specify the version of Web Author and the browser you are using when reproducing this behavior?

Best,
Cosmin

[ArthurP]

Hi Cosmin,

I'm using Firefox 148.0 and webauthor 28.0.0.

Regards,
arthur

[cosminef]

Hello Arthur,

Thank you for the details.
To confirm our understanding:

• The lag happens when you have two custom actions that extend AbstractAction and change tracking is on.

• The lag stops if you use only one such action, or if you accept all changes (so there are no tracked changes left).

• So the issue only appears with both conditions: two AbstractAction-based actions and change tracking active.

To move forward, could you please:

• Send a Performance trace from when the lag occurs: In FireFox DevTools, open the Performance tab, click "Start recording", type a few characters so the lag happens, then Stop. Use "Upload local profile" and download the file. Send us that file.

• Confirm the exact steps you use to reproduce the lag (e.g. open document → enable change tracking → type in a specific place), so we can try to reproduce it on our side. For this, it would be helpful if you could provide the document where you reproduce the issue, as well as the plugin/framework that contains the two actions.

If needed, we can continue this discussion through our official support address: support@oxygenxml.com

Best,
Cosmin