Creating block references to lists within callouts leads to formatting issues

[hxxsx]

Steps to reproduce

You can try using the file I provided or use the following code yourself:
a.md (260 Bytes)
b.md (1.2 KB)

1. Create a new markdown file
   1. Name it a.md, this file is to display format reference errors
   2. Copy the following code into it

- >[!note]
> - aaaaaaaaaaaaaaaa ^1
> 	- bbbb ^2
> 		- ccccc ^3
> 			- dddddddd ^4


- The format is correct but the template is wrong (not a note callout, just a quote): ![[a#^1]]

- Format error: ![[a#^2]]
-  Format error: ![[a#^3]]
-  Format error: ![[a#^4]]

2. Create a new markdown file
   1. Name it b.md, this file is to display format reference errors that cause LaTeX to not parse correctly.
   2. Copy the following code into it

- >[!note]
> - aaaaaaaaaaaaaaaa ^1
> 	- bbbb ^2
> 		- ccccc $\begin{vmatrix}\phi_{1}(x) & \phi_{2}(x) &\dots &  \phi _{n}(x)\\ \phi'_{1}(x) & \phi_{2}'(x) & \dots & \phi'_{n}(x)\\ \vdots & \vdots  & \dots & \vdots \\ \phi_{1}^{(n-1)}(x) & \phi_{2}^{(n-1)}(x) & \dots &  \phi _{n}^{(n-1)}(x)\end{vmatrix}$ ^3
> 			- dddddddd $$\begin{cases}a\\b\\c\end{cases}$$ ^4
> 			- $\begin{vmatrix}\phi_{1}(x) & \phi_{2}(x) &\dots &  \phi _{n}(x)\\ \phi'_{1}(x) & \phi_{2}'(x) & \dots & \phi'_{n}(x)\\ \vdots & \vdots  & \dots & \vdots \\ \phi_{1}^{(n-1)}(x) & \phi_{2}^{(n-1)}(x) & \dots &  \phi _{n}^{(n-1)}(x)\end{vmatrix}$ ^5
> 			- $$\begin{vmatrix}\phi_{1}(x) & \phi_{2}(x) &\dots &  \phi _{n}(x)\\ \phi'_{1}(x) & \phi_{2}'(x) & \dots & \phi'_{n}(x)\\ \vdots & \vdots  & \dots & \vdots \\ \phi_{1}^{(n-1)}(x) & \phi_{2}^{(n-1)}(x) & \dots &  \phi _{n}^{(n-1)}(x)\end{vmatrix} $$ ^6


- The format is correct but the template is wrong (not a note callout, just a quote): ![[b#^1]]

- Format error causing LaTeX to not work: ![[b#^2]]
- Format error: ![[b#^3]]
- Format error.At the same time, we can see that the references are incomplete; they do not include information for ^5 and ^6: ![[b#^4]]
- Format error: ![[b#^5]]
- Format error: ![[b#^6]]

Expected result

1. Hope to correctly reference the list format in callouts.
2. If possible, make the style the same, such as the >[!note] format instead of the ordinary > format.

Actual result

As shown in the sandbox environment For the file a.md, used to display incorrect format references source-view pre-view

We can see that for ^1 we can reference normally, but the style is not correct, and for ^2 ^3 we cannot reference correctly

For the file b.md, used to display incorrect format references that cause LaTeX to not parse correctly source-view pr-view We can see that for ^2 ^3 the format error causes LaTeX to not parse correctly

SYSTEM INFO:

Obsidian version: v1.6.3
Installer version: v1.5.11
Operating system: Windows 10 Enterprise 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: 9
Plugins enabled: 9
	1: Latex Suite v1.9.3
	2: PDF Highlights v0.0.4
	3: Annotator v0.2.11
	4: Canvas Links v1.1.4
	5: Link Exploder v0.3.0
	6: Canvas2Document v1.2.0
	7: BRAT v1.0.1
	8: Canvas Block Reference v0.0.4
	9: Hover Editor v0.11.20

[hxxsx]

I think this issue is quite simple, actually, it’s formally because of the ‘>’ symbol. If we remove the ‘>’ symbol, the normal list will not have any problems. The issue is with the spacing between the ‘>’ and ‘-’ symbols. It affects whether it can be displayed normally. However, the callout feature is very useful, so I think it’s necessary to fix this bug. For example, when we make notes on the original information, we need to use callout to distinguish the original information from our own notes.

[rigmarole]

I only skimmed, but this seems similar or identical to this issue, which seems to be fixed in 1.6.4. Filename changes are prepending weird things to my files - #17 by rigmarole

There might be an existing bug report as well.

[hxxsx]

Thank you for your reply. I looked it over and it seems like it’s not the same issue. The problem with the table is caused by the spacing between the “>” symbol and the “-” symbol.

[WhiteNoise]

We currently do not support block reference to individual elements within a callout, only to the callout as whole.

Please open a Feature Request.