Although I agree that this bug fell over into associability issues.
But original post this issue was moved is Accessibility: Keyboard navigation and shortcuts for dialogs and pop-up modals
It’s about general navigation in an editor. To implement this properly would take quite a lot of research. And tasks like this usually gets lower priority.
But that I’ve reported is more about Editing experience and directly impact how users can type.
With current state only way to fix misspelled word is to use mouse. That may slow down many users (especially ones that write in non native language) by a lot.
I feel like by merging this issues (and couple similar) into overall application Accessibility mixing different types of user experience in one.
Navigation vs Text editing.
I believe we need to have own issue for context menu since it’s about Editing experience and basic expectations from user (it works this way in most existing applications and browsers).