I was wondering if there was a policy about enabling the tab key when editing markdown. I was recently composing a list and I wanted to indent, so I hit enter, tab, -, and then space, which triggered the “reply to topic” action unintentionally.
It would be fantastic if users could set a preference to enable the tab key inside text editors.
I’m sorry if this has been discussed before. What do people think?
Yeah, I totally understand that this would be non-standard behavior and less accessible. The right solution, I think, would be to enable it only by user opt-in.
As we all know, when working in a desktop editor, the tab always adds spaces. The problem is the choice of using the same key (tab) to do two completely different things.
This has always bugged me. And I realize it’s not specific to Discourse. But it’s my understanding that Discourse is about ‘reimagining what a modern Internet discussion platform should be today’.
I’m wondering how other people handle it. I fully understand and appreciate the browser convention. This doesn’t change the fact that tab is valid content. Also, it’s preserved when copying and pasting content into the editor. I see it as 2 separate but overlapping issues.
The browser convention issue is resolved with…
But that leaves the content issue.
I’m not bringing this up just to be pedantic. I’m playing around with Discourse as a place to post code and markup snippets and this is something that does come up.
this is a very old topic, so maybe there’s fresh stuff going on, but I’m with Jeff on ‘tab’ meaning field to field. so I came here to ask how I can change this:
tab followed by enter leads to posting the topic/reply.
which is seriously inconvenient in my case. Any suggestions on how I can stop that? thanks!