Malfunction Toc with Heading Level 1 in read-only

[AstroMichi]

Description

I copied a long text from an other text editor where is enabled Heading level 1, and because of his length in read only mode is possible to see Headings 1 in toc,

TriliumNext Version

0.102.2

What operating system are you using?

Windows

What is your setup?

Local (no sync)

Operating System Version

Windows 11

Error logs

[dosubot]

Hi @AstroMichi! I'm Dosu and I’m helping the Trilium team.

This looks like it stems from how Trilium handles H1 headings. Trilium reserves H1 for the note title itself, so content headings are expected to start at H2 [1]. When you paste content from another editor that contains H1 elements, those become "rogue" headings that the TOC wasn't designed to display cleanly.

There's actually an inconsistency in the codebase here: the read-only mode TOC queries the DOM for "h1,h2,h3,h4,h5,h6" [2], meaning it picks up H1 elements, while the share theme TOC explicitly excludes H1 by only querying "h2, h3, h4, h5, h6" [3]. The TOC's nesting logic starts at level 2 and includes defensive handling for "rogue h1 elements" [4], but it may still display them incorrectly since the hierarchy assumes H2 is the top level.

Workaround: Select the pasted headings in edit mode and change them from H1 to H2 (or deeper). Trilium's editor only offers H2–H6 in its heading options, so this aligns with the expected structure.

The read-only TOC selector including H1 (unlike the share theme) could arguably be considered a bug — it should probably be consistent and exclude H1 as well.

To reply, just mention @dosu.

---

Docs are dead. Just use Dosu.