A minor issue: autocompleting of tags won’t work when the # is the first character of a line.
AI-generated summary
Users report that tags won’t autocomplete when typed at the start of a line, which is by design due to Markdown’s heading syntax (# header). While this avoids confusion with headers, it causes usability issues for communities relying heavily on tags, leading to mistyped or unlinked tags like #Wrong-Tag-Name. sam proposed a minor refinement: wait for one more character after # (e.g., #b) before triggering autocomplete, rather than giving up immediately. renato emphasized the impact on user experience and confirmed this is a known issue, previously reported here. osioke noted the design intent — users typically write content first, then tag — but acknowledged the friction. Richie shared screenshots illustrating the broken behavior at line start versus mid-sentence. sam labeled it pr-welcome, inviting community contributions. renato later noted the issue appears resolved via this update, suggesting improvements to hashtag handling may have addressed the limitation. The discussion reflects a balance between Markdown conventions and user workflow needs, with a clear path for community-driven fixes.
Not really a bug, but might be confusing if you are unfamiliar with markdown. Lines beginning with # means something in markdown, and it’d be weird if I saw a list of tags or categories every time I’m writing a header.
# a header renders to:
a header
You can add a space before the # as a workaround.
4 Likes
Well, the header requires a space between the # and the first character, a tag doesn’t. So technically there’s a difference, no?
Its a trade-off
- Be really annoying out of the box when you try to create titles
vs
- Autocomplete for tags/categories
I see a minor feature request here which is fine for, when you are at the beginning of a line:
#b 
autocomplete appears.
So we basically wait one more char instead of totally giving up.
6 Likes
I understand it’s a minor feature request, but is this something that can be achieved somehow?
Tag autocompleting is a key feature in my community and users are just not linking to the tags because the autocomplete doesn’t show up in this specific scenario, and the post ends up with a bunch of #Wrong-Tag-Name.
Thanks.
1 Like
Certainly pr-welcome for this refinement.
4 Likes
Hi everyone,
#tag suggestions and #category suggestions only work mid-sentence and never at the start of a new line.
For example, here’s a mid-sentence example that works: #po
And here’s a new line / start of line that doesn’t work, zero suggestions are offered:
#po
I can’t seem to find any reference to it.
It provides a very mixed user experience.
Is this by design?
1 Like
Yes it is by design. As with conversations, you’d usually start with what you want to say then include a reference or link/tag some other conversation or material to it.
1 Like
Previously reported here:
It’s said to be a limitation caused by the heading markdown, usually when you’re starting a line with # that’s what you want.
However, I use tags extensively in my community and I’d like to target this eventually, users often mistype the tag they are trying to mention. @sam said it’s pr-welcome (allowing the dropdown to appear when you type a letter after the #).
2 Likes
I didn’t realise there was a topic for this already, so I merged the conversation here.
3 Likes
It seems to be fixed with
3 Likes
This topic was automatically closed after 3 days. New replies are no longer allowed.