Is it a specification that backticks for codeblocks are not supported in inline Markdown?

[akisatoon1]

I am experiencing the same issue as reported in mermaid-js/mermaid issue#6201.

In a comment in related other issue#6099, it was mentioned:

I think in general, for both 10.x and 11.x, they do not support block level markdown, such as lists, blockquotes, etc. Only inline markdown, such as bold, italics, etc.

Regarding this, I have two questions:

• Are codeblocks, like `text`, considered block-level?

• Is the lack of support for certain Markdown elements a known specification?

I would appreciate it if you could clarify whether this behavior is by design or a current technical limitation.

[harshagarwalnyu]

Yes, this is by design. Mermaid's markdown support in labels is intentionally limited to inline formatting only, not block-level constructs.

What is supported:

• Bold: **text**
• Italic: *text*
• Some diagrams support [link](url)

What is NOT supported:

• Code spans with backticks (`code`)
• Code blocks
• Lists, blockquotes, headings

This limitation comes from Mermaid rendering its own lightweight markdown subset (not full CommonMark). The intent is to keep diagram label parsing predictable across all diagram types.

Workarounds for monospace text in labels:

1. Theme font override (affects all text):

%%{init: {'themeVariables': {'fontFamily': 'monospace'}}}%%

2. HTML labels (only in diagrams that support htmlLabels, e.g. flowchart):

A["<code>some_code()</code>"]

Note: requires enabling htmlLabels and may not render in all environments (GitLab, Obsidian strip HTML).

3. Unicode monospace lookalikes — impractical but sometimes used for one-off emphasis.

Tracking issue for broader markdown/code-span support: #6201 — upvoting there is the best signal to prioritize it.