Disable default behavior where dragging a file to a folder, expands it

Use case or problem

Dragging a file to a folder, expands the folder by default before dropping the file.

Proposed solution

Allow the user to disable this behavior.
Allow this behavior to work, only if the user chooses a modifier, for example option or command on Mac.

Example: I disable the feature completely when it comes to just dragging the file(s) and then hovering over a folder. If I then press the modifier, it expands the folder underneath the cursor, before I drop the file(s). This can happen (the modifier expanding folders), for as many times as I want for sub folders, until I finally drop the file(s) when I let go of the mouse button. So, the modifier is pretty much a trigger to expand the folders, only when I’m dragging files.

macOS allows this using the spacebar. When I hit the space bar, it puts me inside that folder.

I had the very same issue, the solution is to deactivate the Auto-reveal current file button.

You find this button on top of your file tree. Please see the picture

Let me break this down into 2:

1 - I’m using the Notebook Navigator plugin, so that button is not available. I will have to probably ask the developer if this is something he can change and then implement the modifier part of my “solution”.

2 - Even when I go back to the default Obsidian view and I see that button, with or without it activated, I get the same behavior. When I drag a file to a folder and don’t drop it, the folder still expands.

I remember, not long ago, that having that button activated was indeed causing a behavior I didn’t want, but I can’t quite remember what it was. It was fixed once I turned it off. I just think it’s not the same issue now.

Even if that was fixing the issue, the modifier route was still something that could be implemented, so we don’t lose that feature completely.

I see. Sometimes plugins load with unexpected settings. Luckily, most plugins can be configured to suit our needs.

If you’ve css snippets, deactivate them and check if your folder behaves differently.

If not, try to check plugins.
So, deactivate community plugins.

If plugins are the cause, re-activate community plugins and deactivate the plugins you use most to find out where the error hides.

Finally, you can try if you get the same error in Obsidian’s sandbox vault.
If yes, you could roll back to a previous version of Obsidian. Just download a previous version from Obsidian’s GitHub page.

I forgot, if your navigator plugin causes the issue and there’s no option/toggle available, you better contact the plugin author on GitHub to report the issue.