[Bug] Footnotes change to bulleted lists in Reading view

[Calion]

Platform

[x] iOS
[ ] Android

Obsidian Mobile version: v1.4.1

---

Steps to reproduce

1. Create a note with some footnotes.
2. View in Reading view.

Expected result

Footnotes rendered as footnotes, with footnote marks.

Actual result

Footnotes rendered as a bulleted list, with no footnote markers in the footnotes section.

[Calion]

Is anyone else seeing this?

[anon63144152]

The thread below is similar and has a CSS fix. Don’t know if it could be used for footnotes as well as numbered lists:

[Bug] Numbered list changes to unordered list in Reading View

Platform [x] iOS [ ] Android Obsidian Mobile version: 1.0.03 I noticed that a numbered list (unindented, first-level) seems to display as a bullet list in the Reading View on iOS platform. I appreciate if anyone can shed some light on this issue. [source: imgur.com]

And:

[Bug] Numbered list changes to unordered list in Reading View

Steps to reproduce Create several footnotes including an inline footnote and the corresponding explanations at the end of the note. Expected result In reading mode, I expect to see the explanations of the footnotes along with the corresponding reference number. Actual result In reading mode, footnotes are displayed at the end of the note as an unsorted list without the corresponding reference number. See attached screen shot. Environment Debug info: SYSTEM INFO: Operating system: i…

[zanodor]

I hardly use lists in my texts but my footnotes were sorted with the CSS mentioned there.

Also, I used regex in Notepad++ to separate individual footnotes by empty lines as sometimes Obsidian merged/referenced several or all footnotes as one (not every footnote had the arrow sign).

[Calion]

I’m also seeing situations where Obsidian isn’t recognizing the second footnote in Reading view, and just has a 2: and the second footnote text immediately following the first.

This, along with the “Numbered list changes to bulleted list” bug, are reasonably serious bugs! They certainly meaningfully degrade usability. Please address this!

[WhiteNoise]

this was fixed in 1.4.2