Nested blockquotes are rendered wrong in reading mode

Steps to reproduce

Inside a note, start a new blockquote, with a nested blockquote inside, and then finally another line on the original blockquote level, like this:

> level 1
> > level 2
> level 1 again

Switch to the reading mode, and observe how the last line (“level 1 again”) is pulled into the nested blockquote above it.


Did you follow the troubleshooting guide? [Y]

Expected result

The lines “level 1” and “level 1 again” should be on the same level of indentation.

Actual result

The last line of the blockquote is pulled into the nested blockquote and has an indentation of 2 instead of 1.


Obsidian version: v1.5.3
Installer version: v1.4.13
Operating system: Windows 10 Pro 10.0.19045
Login status: not logged in
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 1
Plugins enabled: 0


Additional information

The rendering is fixed when there’s an empty line after the nested blockquote with the original level of indentation:

> level 1
> > level 2
> level 1 again

This probably happens because a blockquote will implicitly be continued until it’s ended by an empty new line. Setting an explicit nesting level should overrule that implicit behaviour though.

This will render into a blockquote with three lines, displaying the implicit continuation of blockquotes:

> This is a blockquote
that's implicitly extended
even though only the 1st line starts with a >

This line is not part of the blockquote anymore

no, reader is correct.

for the same reason of this

> level 1
still level one

Moved to help

I guess then the live preview is wrong - the live preview and the reading mode should show the same thing. I’d love to adjust the original post accordingly, but Discourse won’t let me edit it anymore.

Shouldn’t the explicitly set nesting-level have precedence over the implicitly inherited level from the previous line though?

Live preview and reading mode use different markdown engines, with the latter being mostly according to standard, and the first easier to work with in an editor setting.

We would all like for there to be only one engine, but for the time being we just need to adapt to it.

1 Like

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