Outline formatting is misleading/misaligned when only some nodes have children

Obsidian 0.16.2 - standard Dark theme.

Consider the following Markdown:

# H1 - first

# H1 - second

## H2 - Example 1

## H2 - Example 2

# H1 - third

# H1 - fourth

Currently, this is rendered like this: (colored lines added for emphasis)

CleanShot 2022-09-05 at 12.13.15

It makes it appear as if H1 - second is a child of H1 - first, when in fact it isn’t. I don’t know if this can be fixed with CSS or if it requires under the hood changes.



1 Like

moved to FR

1 Like

Feature request? why? this is a regression


We appreciate the feedback but we don’t see it a bug.

And I’m only 5’8"

I don’t see myself as short :neutral_face:

1 Like

This is definitely a bug, not a feature. But if this is the Obsidian developers’ quirky way to prioritize, then I guess, so be it.


Commenting here as I made a post on the same issue, but I also noted that the File Explorer has the same issue.

1 Like

This is seriously confusing. And at least on Mac and iOS, it also goes against the system standard (see how Finder and Files do it).

Here’s a link to Ruq’s closed post on the issue:

1 Like

today I found a article shows a way to use only css to achieve the good align tree view:

maybe someone good at css can work out a custom css sniplet with it, to give us peace of mind before this bug been fixed by obsidian team.

The problem seems to be fixed in note bodies, but not in the file explorer.

Here’s the snippet I was using. I’ve been meaning to try to adapt it to the file explorer, but maybe someone else (preferably the developers) will get to it first.

/* Move folding arrows out of the flow so items on the same level have the same indentation. */
/* Source: sailKite @ https://discord.com/channels/686053708261228577/702656734631821413/1034243460930207774 */

.tree-item-inner:first-child {
    position: relative;
    padding-left: calc(2 * var(--size-2-3));
.tree-item-inner:first-child::before {
    content: "";
    position: absolute;
    height: calc(100% + (2 * var(--size-4-1)) + 1px);
    left: 0px;
    top: calc(-1 * var(--size-4-1) - 1px);
    width: 2px;
    border-left: var(--nav-indentation-guide-width) solid var(--nav-indentation-guide-color);
.is-collapsed + .tree-item .tree-item-inner:first-child::before,
:is(.is-collapsed + .tree-item) ~ .tree-item .tree-item-inner:first-child::before {
    content: none;

It goes against how the file explorer does it on Windows, too.

[Merged from “Bug reports”/“Wrong indent for same level titles in outline view”]

Steps to reproduce


## section-1
### sub-section
## section-2
## section-3
### sub-section

Expected result

Same level title should have the same indent

Actual result



  • Operating system: Win11 Home Edition
  • Debug info:
	Obsidian version: v1.1.9
	Installer version: v0.15.8
	Operating system: Windows 10 Home China 10.0.22000
	Login status: not logged in
	Insider build toggle: off
	Live preview: on
	Legacy editor: off
	Base theme: dark
	Community theme: none
	Snippets enabled: 0
	Restricted mode: off
1 Like

Are there any plans to change this in future updates, or does this post’s relocation to FR imply it was intentional and here to stay?

In my opinion, the outline has lost some of its value as a quick reference.

In theory, left-justifying the text of #H1 with the dropdown arrow of #H2 seems reasonable as you’re aligning the first character of each row, but that discounts the effects of visual perception. The text chunks are perceptually grouped because they share similar qualities (shape, spacing, color, etc) and those groups are interpreted as vertical lines… lines which are no longer straight, which doesn’t accurately convey the hierarchy.

1 Like

The devs use a narrow definition of “bug”. There’s no guarantee this will be addressed, or addressed soon, but if they rejected the idea it would be closed, archived, or moved to Help.