Might be related to DOMObserver usage. It appears that Chromes javascript profiler is obfuscating whatever is long running.
Ok, finally reporting something interesting; the text in the table I was working with had spelling corrections pending, and it appears Google chromes implementation has to refire on every interaction.
I am aware of some threads about spellcheck but I was not aware of the performance ramifications being this deep. Is is possible your table is filled with non-English characters that your browser is attempting to correct as well?
Performance stabilized by adding the spellcheck=false attribute to just the
element.@marijn Thoughts on this? I reached out to a prosemirror-table author and he said he wasnt working on it anymore; Been trying to improve performance there (2 open PR’s) but this spell check one might be heavily effecting non english Chrome browser users more than anything. Im not sure if its related to prosemirror-tables and its DOMObserver usage or a core prosemirror library
Edit: I see this comment now - What is the current state of spellcheck? - #11 by marijn