Steps to reproduce
Create a Note, let’s call it Test, contains
| A |
| --- |
| a |
| B |
| --- |
| b |
Embed that in another note, call it test2, with content
![[Test]]
That all works fine, now modify the original note by putting both tables inside any one xml tag. I used “split” when doing my sandbox test.
What happens now is that the contents of test are now rendered as text, not markdown (i.e you don’t get tables, you just get the raw markdown), but Test2 is still properly rendered as the two tables. The default behaviour is obviously to stop markdown rendering inside tags, possibly because there are issue with html/markdown interaction as outlined in #5470, but this default behaviour is overwritten for embedded notes, which behave as one might want.
Why this matters is that that the use of this particular tag (split) is integral to the behaviour of the advanced slides extensions, and I would argue that the use-case is important enough (and the inconsistency of behaviour jarring enough) to call this a bug, not a feature request :-).
Ideally, one would alter the obsidian rendering engine to behave the same whether embedded or not, and choose the embedded option. However, I can see that there might be backwards incompatibility issues if one simply changed the behaviour, so a possible solution would be to either only do this for the one tag: split, or better and more future proof, to parse such tags and look for an optional attribute like “render-markdown=True” and respect that (or not) in both native notes and embedded notes.
Did you follow the troubleshooting guide? [Y]
Expected result
- Described Above
Actual result
Described above
Environment
SYSTEM INFO:
Obsidian version: v1.9.12
Installer version: v1.8.3
Operating system: Darwin Kernel Version 24.6.0: Mon Jul 14 11:30:51 PDT 2025; root:xnu-11417.140.69~1/RELEASE_ARM64_T8112 24.6.0
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0