<div> breaks links to headers

Steps to reproduce

Insert a <div></div> pair into any note that has headers. Headers following the <div> tag do not appear in link autocomplete after typing #, and in fact can’t be linked to even if typed manually. If the <div> is at the top of the document, no headers will appear.

Did you follow the troubleshooting guide? [Y]

Behaves like this in the sandbox.

Expected result

Headers are available despite the presence of <div> tags

Actual result

Headers after <div> are ignored

Environment

SYSTEM INFO:
Obsidian version: v1.8.10
Installer version: v1.8.4
Operating system: Darwin Kernel Version 24.5.0: Tue Apr 22 19:54:33 PDT 2025; root:xnu-11417.121.6~2/RELEASE_ARM64_T8122 24.5.0
Login status: not logged in
Language: en
Insider build toggle: off
Live preview: on
Base theme: light
Community theme: Cupertino v1.7.4
Snippets enabled: 1
Restricted mode: off
Plugins installed: 33
Plugins enabled: 32
1: Dataview v0.5.68
2: Auto Link Title v1.5.5
3: Customizable Sidebar v2.2.1
4: Local images v0.14.2
5: Local REST API v3.2.0
6: Minimal Theme Settings v8.1.1
7: Tag Wrangler v0.6.4
8: Templater v2.11.1
9: Editor Syntax Highlight v0.1.3
10: Emoji Shortcodes v2.2.0
11: Iconize v2.14.7
12: Sort & Permute lines v0.7.0
13: Style Settings v1.0.9
14: Spaced Repetition v1.13.3
15: Homepage v4.2.2
16: Advanced URI v1.44.3
17: Excalidraw v2.12.1
18: No dupe leaves v0.0.12
19: Map View v5.5.0
20: Sheet Plus v1.11.9
21: Copy Image v1.1.0
22: Paste image rename v1.6.1
23: Ribbon Divider v1.1.1
24: Waypoint v2.1.0
25: Manual Sorting v2.4.0
26: File Cleaner Redux v1.7.0
27: WordCraft v1.1.1
28: Folder notes v1.7.35
29: Force note view mode v1.2.2
30: Number Headings v1.16.0
31: Text Format v3.1.0
32: Extended Markdown Syntax v2.0.11

RECOMMENDATIONS:
Custom theme and snippets: for cosmetic issues, please first try updating your theme and disabling your snippets. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community theme and snippets.
Community plugins: for bugs, please first try updating all your plugins to latest. If still not fixed, please try to make the issue happen in the Sandbox Vault or disable community plugins.


Additional information

Although it affects me, I think this is quite a low priority. It may be this is an unavoidable side-effect of mixing HTML spans in markdown documents, and if so, it’s not the end of the world if this behavior is just the way it is.

This is not a bug. We explicitly do not support intermingling block-level HTML elements (like div) and Markdown.

All HTML block-level code must be contained in a single Markdown block (that is, no blank lines).

Thanks, good to know, and that seems quite reasonable.