Bug/Usability: Browser history affected by using URL to control modal

Bug/Usability: Browser history affected by using URL to control modal

It seems that the state of the file details modal is controlled via a URL parameter (opendetails=true).
Example:

• File list: /apps/files/files/403980?dir=/Talk
• File details modal: /apps/files/files/403980?dir=/Talk&opendetails=true

This causes each modal open/close action to be recorded in the browser history.
When the user tries to go back to the previous folder, they first need to "rewind" through multiple modal openings, which compromises usability.

The same behavior happens when opening a file. After closing it, if we try to go back to the folder, the browser reopens the file instead, since the history was affected.

Steps to reproduce

1. Open a directory.
2. Open the details of a file several times (modal).
3. Try to use the browser’s back button.

The browser goes through all modal open/close states before returning to the previous folder.

Personally, I would prefer that opening/closing a modal is treated as a UI interaction, not as actual navigation.
The back button should take the user directly to the previous folder.

I also notice the absence of a more defined routing system for directories/files.

If there is already any discussion about this, I would like to follow it.

Start by reproducing the issue in the file list using the example URLs and the listed back-button steps. Trace how opening and closing the file details modal changes the URL and browser history, then confirm that navigation returns directly to the previous folder without replaying modal states.