HTML Elements Display Incorrectly in Live Preview in Footnotes

HTML elements do not render correctly in Live Preview when they’re the first thing in a footnote.

Steps to reproduce

  1. Create a footnote with an HTML element at the very start.
  2. Observe that the element does not display in Live Preview.

Note that HTML elements do display correctly as long as there’s text before them in the footnote; see footnotes 3 and 4 in the example.

Did you follow the troubleshooting guide?

Yes. Reproduced in a sandbox vault.

Expected result

I expected the HTML elements to display in WYSIWYG style.

Actual result

The HTML is shown as-is in Live Preview.


	Obsidian version: v1.3.5
	Installer version: v1.1.9
	Operating system: Windows 10 Home 10.0.19043
	Login status: not logged in
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 0
	Restricted mode: on

Additional information



[^1]: <ruby>脚<rt>きゃく</rt>注<rt>ちゅう</rt></ruby>
[^2]: <span style="color: var(--color-blue)">blue</span>
[^3]: . <ruby>脚<rt>きゃく</rt>注<rt>ちゅう</rt></ruby>
[^4]: . <span style="color: var(--color-blue)">blue</span>


Footnotes are complex and what you are doing I am not even sure it’s standard markdown.
Anyway, I’ll add this bug report.

You said “yes”, but one of the steps in the guide is updating your Obsidian installer. Your installer seems pretty out of date at v1.1.9.

This is just a side note. Updating the installer won’t change this particular issue. But you should consider downloading and reinstalling occasionally.

Thanks for the response!

I am not even sure it’s standard markdown.

This is neither here nor there, but I’m not too sure what you mean by this. The original (informal) format and CommonMark both don’t include footnotes. The former does assert that HTML blocks should be isolated on their own line, but if this were a strict rule then the same would apply to HTML within lists, blockquotes, tables, et cetera.

I don’t deny that footnotes are complicated, but I’d nonetheless love for this admittedly rare edge case to be addressed eventually! :smile:

Also, @rigmarole, thanks—I must have missed that. I’ve updated it now.

will be fixed in v1.6.0

This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.