When a ProseMirror editor is focused using the keyboard (i.e. by pressing Tab), it usually gets the
ProseMirror-focused class and the cursor is positioned at the start of the editable content.
However, in Chrome (but not Firefox, where the cursor is positioned as expected), if the first editable node has a node view that adds an element with
contenteditable=false at the start of the view, the editor is still focused but the cursor isn’t visible and the editable node isn’t focused.
I’ve made a minimal example that shows this behaviour.
ProseMirror’s behaviour is actually better than native contenteditable in any browser, but it would be nice if it could always focus the contentDOM in Chrome in the same way it does in Firefox.