Potential bug: Markdown files and strikethrough

[GLeeSC]

Has anyone else experienced an issue with markdown files (.md) and single tildes triggering strikethrough?

I believe that in Markdown, a double tilde (~~) should trigger this.

I am reviewing a file right now, and have this in the file:
"~8/10 orgs".

When I have Phoenix show me the file, the sentence is struck through until the next tilde is encountered despite this being a single tilde.

I think this is a bug?

Running Phoenix Code 5.1.24 (not Pro version), MacBook Pro (Apple M2) and Tahoe 26.5.1.

I copied and pasted the text into other .MD file rendering apps and no strikethrough was seen.

[abose]

Thanks for reporting the issue @GLeeSC
Did you mean the strike through happens in the live preview or on the code editor? I am unable to see strike through with a single ~ . Can you paste a screenshot here with a limited doc here, it will help to understand the exact issue.

It looks like the preview is working as expected in my case, but the coding surface is showing strikethrough on a single ~ which is unexpected.

[UnknownHawkins]

The behavior you see is not part of the official Markdown spec - strikethrough is only activated with a double pair of tildes (~~).
Phoenix’s preview renderer has a small regex bug that mistakenly treats a single tilde as the start of a strike‑through span.
It only triggers when the parser reaches the next matching character (the second tilde), so the text from the first tilde to the next one gets crossed out.

Until the renderer is fixed you can work around it by:

\~8/10 orgs # escape the tilde
or
`~8/10 orgs` # inline code

If you’re consistently seeing this issue, let the Phoenix team know. They can patch the regex or add an option to disable the “tilde → strike” shortcut in the settings.

[abose]

Did you mean strike through is not working ad expected in the code editor or the live markdown preview.

In the editor, we have a known issue to be fixed as seen in the screenshot.