You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If focus event is dispatched on one of nodes with-in the editor prosemirror does not handle it. For example if there is a tabindex attribute present on the paragraph or heading nodes using Tab / Shift-Tab key combination dispatches focus event on a corresponding node (which does not bubble up if container is focused) so prose-mirror does not handle it in any way.
It is also won't make it into handleDOMEvents for the same reason.
ProseMirror's focus handling concerns focus of its top-level editable node. Focus on children of that is intentionally not handled—and setting a tabindex on a paragraph isn't something the system supports.
Issue details
If focus event is dispatched on one of nodes with-in the editor prosemirror does not handle it. For example if there is a
tabindex
attribute present on the paragraph or heading nodes usingTab
/Shift-Tab
key combination dispatches focus event on a corresponding node (which does not bubble up if container is focused) so prose-mirror does not handle it in any way.It is also won't make it into handleDOMEvents for the same reason.
Steps to reproduce
Here is an example that adds
tabindex=0
attribute to theparagraph
andheading
nodeshttps://glitch.com/edit/#!/join/a592d66e-470c-4c5d-a7d9-9c351aae426d
If you press
Tab
/Tab-Shift
you'll see an outline appearing on o corresponding node but selection will remain in it's original location.I would expect
Tab
/Tab-Shift
to update selection so that content of the corresponding paragraph / heading is selected.ProseMirror version
"prosemirror-view": "1.2.0"
Affected platforms
The text was updated successfully, but these errors were encountered: