Initial Lag When Dealing With Initial Text Content Containing Only New Line Characters

[twosixfoursix]

Greetings,

I have not filed this as an issue since I do not yet know whether this is due to an error on my part or has something to do with how Android's WebView behaves rather than it being an issue with ace editor. I am unable to reproduce this issue on desktop browsers.

For one-off renderings within my a sandboxed environment, I set specific global variables before the browsers starts and call an init function within the load event of the page which creates the entire editor using the global variables setting the theme, language mode, indent size, initial string content, etc.

The behavior occurs regardless of whether I create a new session or add the initial string on as the value argument in the editor options.

When the text only contains empty lines - specifically \n, there will be considerable lag/stalling. The problem is however fixed if there is at least one visible char within the string or the showInvisibles is set to true.

I have provided some video reference, the black background is to make delays more noticable.

Handling of files containing only \n vs. files containing other text content.

nonworking.mp4

With showInvisibles is set to true

working.mp4

Checklist:

• Value was read as & passed as UTF-8 string.
• Characters escaped on Java/Kotlin side with an additional backslash were \, ` & {
• The initial content string was assembled as window.filedata = `... ... ...`; which would then be set via .setOptions({ ..., value: filedata, ... }); or .createEditSession(filedata, ...); with window.filedata being passed as an argument to the init function.
• On WebView debugging side, the logs state javascript side receiving data much earlier with strings properly constructed as how javascript would expect them.
• Changing or omission of newLineMode has no effect.

Please let me know about your thoughts on the matter.