Callout in canvas text node causes infinite loop

[ush]

Steps to reproduce

1. Create a new Canvas file
2. Add a card (text node) and insert a callout in it. The resulting canvas file will look like this:

{
	"nodes":[
		{"id":"d22017114893768b","type":"text","text":"> [!NOTE] Title\n> Contents\n","x":-140,"y":-168,"width":420,"height":268}
	],
	"edges":[]
}

3. Double-click the card and activate the card’s editor.
4. Click outside the card to deactivate the editor.

Did you follow the troubleshooting guide? [Y/N]

Y

Expected result

No error

Actual result

Infinite loop causing error messages saying “Uncaught ResizeObserver loop completed with undelivered notifications”

Environment

SYSTEM INFO:
Obsidian version: v1.8.9
Installer version: v1.8.9
Operating system: Darwin Kernel Version 22.6.0: Mon Feb 19 19:43:41 PST 2024; root:xnu-8796.141.3.704.6~1/RELEASE_ARM64_T8103 22.6.0
Login status: logged in
Language: en
Catalyst license: insider
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: off
Plugins installed: 0
Plugins enabled: 0

RECOMMENDATIONS:
none

---

Additional information

[noobydoo]

Something similar is happening to me with different code. Would like to know how to break the loop if anyone would be so gentle as to help out.

Bonus question: how to find the origin of the loop when you just see the error but do not know what piece of code is causing it?

[techy-robot]

I have experienced this exact same issue, with some data view queries in-canvas. It doesn’t always show up though.

[WhiteNoise]

thank you

[ferAzvdo]

Having this issue as well in canvas and notes with embeds inside them. Haven’t figured out how to stop the loop

[ferAzvdo]

Can’t edit the comment again, but I tested it out a bit more

Any embed (I tested with embedding a block link, a note, and a canvas) will lead to a ResizeObserver loop. This only happens right after adding. If I close and reopen Obsidian again, the embed is rendered normally and no loop is generated

[WhiteNoise]

Will be fixed in v1.9. No ETAs.