Feature Request: onContentError() works for setContent()

[oscarlevin]

Description

As far as I can tell, using tiptap-react 2.11.5, the onContentError works correctly when there is invalid HTML set as the initial content, but not when it is set using setContent(). I might be missing something, but it would be really helpful to be able to use this callback in both cases. Note that the setContent() does respect the enableContentCheck correctly, but I just get an uncaught error in the console.

Use Case

I'm working on a VS Code extension that would allow visual editing of XML documents. I suspect it will be quite common for the text editor to send invalid source to the visual editor.

Type

Other