I'm asking because you have making the textarea more accessible as one of your motivations, but then removed tab functionality from the user - which actually causes the post to not be accessible because trying to navigate the first codepen traps the user.
Even if you move the functionality to another key, you're moving the functionality away from where the user is expecting it, and I'm not sure how you would notify the user that they now need to push something other than tab to navigate out of the box.
I'm asking because you have making the textarea more accessible as one of your motivations, but then removed tab functionality from the user - which actually causes the post to not be accessible because trying to navigate the first codepen traps the user.
Even if you move the functionality to another key, you're moving the functionality away from where the user is expecting it, and I'm not sure how you would notify the user that they now need to push something other than tab to navigate out of the box.
Yeah, that's right. I've thought about it but I got no ideas, so I didn't mention it too much in the post.
Do you have any ideas on how to fix it?
I think the solution is to not modify the tab functionality and include a snippet shortcut for adding tab literals?
Good idea! I think what we could do is add another keybinding for inserting a tab, maybe alt + tab