Hey wonderful discourse maintainers,
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?
Hmm, I’m pretty sure that this would hurt accessibility, but it might be a good idea… We already have Ctrl-Enter to submit.
Tab is expected to move from field to field, so this would seriously hurt keyboard accessibility and standard browser conventions.
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.
I can’t even do it in GMail. 
I was thinking something like CTRL+TAB which you would use in Excel, but I’m not finding any online composers that permit this behavior…
In Chrome CTRL TAB takes you to the next… tab.
I think it’s been a poor choice of using the Tab key to move to the next field. But now we have to keep it, it’s too late.
That is browser design 101… You will find that was happening well back in IE 6. So that isn’t a Discourse only issue.
Tab was used to iterate from field to field for as long as I can remember in computer GUIs.
Per Wikipedia, tab as a key to move from field to field in a GUI dates back to at least 1987.
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.
Try it in Notepad 
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.
Cheers
Never gonna happen on my watch. Tab means move to next field in the browser, always has, always will.
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!
我刚刚发现，高亮一行文本并按 Tab 键会缩进它，这是一个相当不错的折衷方案！
显然，如果你选择多行，它也同样适用。
确实如此！这是 @martin 很久以前添加的一个很棒的小功能。
如果我们可以使用 tab 进行缩进就好了。
希望这不会太复杂而无法实现。
这肯定受 Markdown 的限制吧？
Markdown 使用双空格来表示项目符号缩进。
空格用于管理：
在大多数 Markdown 编辑器中，我只需按 Tab 键（或 Shift+Tab 键）即可进入下一（或上一）级。
目前 Tab 键会将我带出编辑器。这肯定有更好的处理方式，对吧？
这在 Discourse 中将非常有价值。
我常常想知道为什么它没有。
在像 Word Perfect、Pagemaker、MS Word 等文字处理软件中，它会根据打字机的功能进行缩进。当然，一旦你移出“编辑器”，它就会像你提到的那样工作。但在文字处理软件的编辑器窗口中撰写文档时，它的功能是缩进。
本着维基的精神 
Tab key - Simple English Wikipedia, the free encyclopedia(short%20for,to%20the%20next%20tab%20stop.\u0026text=In%20word%20processor%20applications%2C%20the,to%20the%20next%20tab%20stop.
在编辑器内部；你处于一个文字处理环境窗口中。
说得有理。制表符键完全可以用来输入空格。
