The strange thing is when I try to look into “selection” in EditorState of the editor in chrome DevTools, the selection there shows the position at end of the line (where it should have been). Which means somehow DOM position changed but prosemirror’s position remained correct.
Please let me know, if it seems like a bug or something I am doing wrong. The code I have is all integrated with my application code. So it is hard to separate it out. But let me know, and I will try to figure out something.
Since this doesn’t happen in the collab demo on the website, it seems to be related to something you’re doing differently. I don’t have enough information to say what, though, and you’ll have to narrow it down before I can say whether it’s a bug in your code or in ProseMirror.
@johanneswilm Most likely I am doing something stupid. I just wanted to check. I am tired trying to debug this issue, so I have kept it aside for a while. I will pick it up in a day or two, and try to isolate it into a separate standalone project, if it still occurs.
We’re seeing some jumbling issues because of character rewriting with an inline span deco. If you haven’t already, you may want to look through how ViewTreeUpdater is dealing with your document and cursor inside NodeViewDesc.updateChildren.
Hello,
I have this same issue, did anyone find a fix for this?
I have no spans near to my cursor and have added a key to my widget as suggested, but it is still happening…thank you