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
I am using editable: false to render a read-only instance, however because of the tabindex="0" when tabbing on the page, focus is being made on the editor. Ideally, since it's not editable, no focus should be allowed on the element so that pressing tab skips the read-only editor and moves to the next focusable element.
How can we reproduce the bug on our side?
Create an editor and set editable: false. Place a text input above and below the tiptap instance. You should be able to tab from input 1 to input 2 without getting stuck on the "read-only" tiptap instance.
Can you provide a CodeSandbox?
No response
What did you expect to happen?
As described above.
Anything to add? (optional)
No response
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. 💖
The text was updated successfully, but these errors were encountered:
What’s the bug you are facing?
I am using
editable: false
to render a read-only instance, however because of thetabindex="0"
when tabbing on the page, focus is being made on the editor. Ideally, since it's not editable, no focus should be allowed on the element so that pressing tab skips the read-only editor and moves to the next focusable element.How can we reproduce the bug on our side?
Create an editor and set
editable: false
. Place a text input above and below the tiptap instance. You should be able to tab from input 1 to input 2 without getting stuck on the "read-only" tiptap instance.Can you provide a CodeSandbox?
No response
What did you expect to happen?
As described above.
Anything to add? (optional)
No response
Did you update your dependencies?
Are you sponsoring us?
The text was updated successfully, but these errors were encountered: