Community feedback on tabbable plugin

[12joan]

Hi! 👋

I'm working on a new plugin that programatically corrects the tab order inside the editor. See the draft PR for details.

Before this plugin is merged, I want to get feedback from the Plate community about potential use cases and pitfalls. Are there any features or changes that would make it easier to integrate the plugin into your app?

You can try it out on the plate-examples Vercel deployment. Check the PR if the link is broken.

Specific areas of interest are:

• Plugin name
  • Renamed from tabbable-voids to tabbable
• Customisation options
• Conflict with existing plugins
• Usability and accessibility issues

Thanks!

[reinvanimschoot]

Do you happen to have a solution involving this plugin when working with nested editors? If you tab into a nested editor, can you come back out to the main editor? We are making heavy use of editable voids and nested editors so this would be amazing! Cheers

[12joan]

I haven't tried it with nested editors. Let us know what issues you run into if you try it. You might be able to resolve them using the plugin options, or by modifying the plugin code in a PR.

[reinvanimschoot]

By default, it doesn't seem to work. When I update the isTabbable to include a nested editor, I can tab into it but not out of it. That's the main issue that we are having. I guess maybe it's a question of adding tabEntry to a node in the main editor.

[12joan]

I'm not sure whether the inner or the outer editor's tabbable plugin would be trying to handle tab events in that case. Possibly both of them. That might be related to the issue you're having.