It would be nice to add Markdown support on the question's title field.
It seems a bit inconsistent when it’s already available in the body and question's comments.
What do you think?
Meta Stack Exchange is a question and answer site for meta-discussion of the Stack Exchange family of Q&A websites. It only takes a minute to sign up.Sign up to join this community
This isn't something we can support.
The big reason is that search engines will not render the formatted title in results. Hence:
How do I move the turtle in LOGO?
.. would look like this in search results:
How do I _move_ the turtle in `LOGO`
.. or similar sorts of messy. This is already a bit of a problem with sites that have MathJax enabled. Their titles can be extremely illegible if you're browsing them from what a search engine returned. While it's a bit of a necessary evil on those sites, as MathJax lets them, well, math and all - I don't see supporting markdown formatting in titles to be any real gain, much less justify the side effects.
There's also the problem with people
parts of people's text
into inline code. I'd hate to also have to deal with that in titles, and we haven't gone into deliberate abuse of the feature yet :)
It's good to want a strong, extremely descriptive and interesting title, but I don't think formatting is going to have a net-positive impact there.
It's intentional to avoid users bolding, or adding italics to make their question stand out.
As such, markdown in full will never be supported in titles.
If you have a good reason to add a specific part of markdown to the title, ask for that and provide a list of existing questions where that feature would arguably improve the questions.
Without examples, though, it's unlikely to gain much traction as a useful feature.
Note that some sites allow MathJax in the titles, so there's a good case for asking this as a feature request for a specific site as well, rather than asking for it network wide:
Asking for a feature in one site rather than all is nice in that it doesn't slow down sites where it's not useful, but as you can see above other sites, and the question hotlist, might not render it correctly.