"Collapse all" button act like "Expand all" when folders are unfolded manually

Steps to reproduce

  1. The button says “Expand all”
  2. Unfold any folder manually, now it says “Collapse all”
  3. Click the “Collapse all” button.

Did you follow the [troubleshooting guide]

Yes, and I ensured the bug is reproducible in Sandbox Vault.

Expected result

All unfolded folders got folded(this is also the result in versions former than 1.5.9).

Actual result

All folded folders got unfolded(the function of “Expand all” button).


Obsidian version: v1.5.11
Installer version: v1.5.8
Operating system: Windows 10 Home China 10.0.22621
Login status: logged in
Catalyst license: insider
Insider build toggle: on
Live preview: on
Base theme: adapt to system
Community theme: none
Snippets enabled: 0
Restricted mode: on



I posted a video on YouTube to show this bug: video

1 Like

Anyone noticed this topic?

Thanks, I did.

Thanks for looking into into it🫡

+1 Came here to post bug report on same issue.

1 Like


Same issue.

With all folders collapsed, manually expanding any folder changes the top button from “Expand all” to “Collapse all”, but clicking it expands all folders. This bug was introduced in the 1.5.11 release.

1 Like

same here

Same here


Same here.

The version was updated today.,But this bug hasn’t been fixed.,Can you raise the priority?,This affects the frequency quite high.

1 Like

Thanks for reporting this. I’ve noticed the same issue in the macOS version.

Same problem (on Android, too).

The bug is present in the iOS version, too.

This is reproducible on v1.15.12 consistently in a vault of any size. I’m getting some bug reports on my plugin for this one: plugin stopped working completely · Issue #43 · nathonius/obsidian-collapse-all · GitHub

This may affect ALL leaves that use the leaf.view.tree model, I’m unsure.


+1 - The latest install 1.5.12 - Installer 1.4.14 (with no plugins) on macOS desktop still exhibits the same behavior. Thanks all!

+1 - Same issue on Ubuntu 22.04 v1.5.12 - Installer 1.4.13

+1 thanks, same issue on MacOS, iirc this issue did not occur in older versions