When capturing the tab key (enabled by default) this can block user who use keyboard navigation from escaping the editor and is an accessibility issue.
There is some discussion about how this can be handled in:
The codemirror option of supporting escape, tab seems like a reasonable one (but maybe that's me showing my vi history).
When capturing the tab key (enabled by default) this can block user who use keyboard navigation from escaping the editor and is an accessibility issue.
There is some discussion about how this can be handled in:
textareaeffectively and move to next focusable? PrismJS/live#8The codemirror option of supporting escape, tab seems like a reasonable one (but maybe that's me showing my vi history).