[Bug]: insertContentAt should either document that it changes selection or it should not change selection

[Nantris]

Which packages did you experience the bug in?

core

What Tiptap version are you using?

2.1.0-rc.11

What’s the bug you are facing?

I find it frustrating that insertContentAt changes the selection. This severely limits its usefulness and this behavior is undocumented. There's no suggestion it will affect selection but it does.

What browser are you using?

Chrome

Code example

No response

What did you expect to happen?

insertContentAt inserts content only, without changing selection.

Anything to add? (optional)

If it's necessary to change the selection then it should come with an option to revert the selection after.

Did you update your dependencies?

• Yes, I’ve updated my dependencies to use the latest version of all packages.

Are you sponsoring us?

• Yes, I’m a sponsor. 💖

[svenadlung]

Hi @slapbox, changing the selection after inserting content is the default behavior. Have you tried this?

editor.commands.insertContentAt(12, '<p>Hello world</p>', { updateSelection: false })

tiptap/docs/api/commands/insert-content-at.md

Line 20 in 6cbc2d4

editor.commands.insertContentAt(12, '<p>Hello world</p>', {

[Nantris]

Wow I just totally missed that option in the docs. Thanks for the tip!

The various options for commands might benefit from being bolded in the docs like:

updateSelection: controls if the selection should be moved to the newly inserted content.

Or alternatively, I'd suggest that yellow background not be used for inline code. It guides the eye a little too much.