Adjacent Citation References Not Rendering Properly in Reading View

Bug reports
1

Issue Description:

When using adjacent footnote citations in Obsidian Markdown, such as [^1] and [^4], the rendered output in reading mode does not display both citations correctly. This issue is particularly evident when one of the citations has been reused earlier in the document.

Steps to Reproduce:

  1. Create a new note in Obsidian.
  2. Add a paragraph with adjacent footnote citations, e.g., [^1] [^4].
  3. Define the footnotes at the bottom of the document:
[^1]: First reference text.
[^4]: Fourth reference text.
  1. Switch between source mode and reading mode.
  2. Observe that one or both citations may fail to render correctly in reading mode.

Expected Behavior:

Both citations should render properly in reading mode, regardless of adjacency or reuse elsewhere in the document.

Observed Behavior:

  • In reading mode, one of the adjacent citations is either missing or rendered incorrectly.
  • This issue persists even after ensuring proper spacing between citations, disabling custom CSS snippets, switching to the default theme, and disabling all plugins.

Supporting Evidence:

The attached screenshots demonstrate the problem:

  • Screenshot 1 (Source Mode): Shows correct Markdown syntax with adjacent citations [^1] and [^4].
  • Screenshot 2 (Reading Mode): Displays incorrect rendering where one or both citations are missing or misaligned.

Troubleshooting Steps Taken:

  • Verified that spaces exist between adjacent citations.
  • Disabled all custom CSS snippets and reverted to the default theme.
  • Turned off all plugins to isolate potential conflicts.
  • Attempted unique citation labels (e.g., [^ref1], [^ref4]) without success.
  • Tested with line breaks (<br>) and non-breaking spaces (&nbsp;) between citations, which did not resolve the issue.

Impact:

This issue significantly affects users who rely on accurate citation rendering for academic writing or detailed documentation within Obsidian.

Request for Resolution

Please investigate this bug and provide a fix in future updates. If additional information is required, feel free to reach out for further clarification or testing assistance.

By following these steps and including this detailed explanation, you can effectively communicate the issue to the Obsidian development team for resolution.