[Bug]: Regression? File move operation in web UI forgets last destination folder since version 28

⚠️ This issue respects the following points: ⚠️

• This is a bug, not a question or a configuration/webserver/proxy issue.
• This issue is not already reported on Github OR Nextcloud Community Forum (I've searched it).
• Nextcloud Server is up to date. See Maintenance and Release Schedule for supported versions.
• I agree to follow Nextcloud's Code of Conduct.

Bug description

Since I moved from NextCloud 28 onwards, I've noticed a change in the web interface behavior when moving files between folders. After moving a file from one folder to another using the "Move or Copy" option, the interface resets to the root directory (or the starting point) when I attempt to move another file. In previous versions, it would "remember" the last destination folder, allowing me to quickly move multiple files to the same location without navigating back each time. Now, I have to manually navigate to the destination folder again for every subsequent move, which significantly slows down the process.

Steps to reproduce

1. Log in to the Nextcloud web interface (version 28 or later).
2. Navigate to a folder containing a file (e.g., /FolderA/file1.txt).
3. Choose the file, select "Move or Copy," and move it to another folder (e.g., /FolderB).
4. Then choose another file and attempt to move another it using the same "Move or Copy" option.
5. Observe that the folder selection dialog resets to the current directory instead of defaulting to the previously used destination (/FolderB).

Expected behavior

After moving a file to a destination folder, the "Move or Copy" dialog should default to the last used destination folder when moving additional files, as it did in versions prior to 28. This would streamline the process of moving multiple files to the same location.

Actual Behavior

The "Move or Copy" dialog resets to the root directory (or initial view) after each move, requiring manual navigation to the destination folder every time.

This change disrupts workflows that involve moving multiple files to the same destination, making the process more time-consuming and less intuitive.

Would it be possible to restore the previous behavior or add an option to "remember" the last destination folder?

Thank you!

Nextcloud Server version

29

Operating system

Debian/Ubuntu

PHP engine version

PHP 8.4

Web server

Apache (supported)

Database engine version

PostgreSQL

Is this bug present after an update or on a fresh install?

Fresh Nextcloud Server install

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

What user-backends are you using?

• Default user-backend (database)
• LDAP/ Active Directory
• SSO - SAML
• Other

Reproduce the behavior in the Nextcloud web interface using the Move or Copy dialog described in the steps, comparing repeated moves in versions before 28 and version 29. Trace the dialog's handling of the previous destination and add coverage for retaining that destination after a move; done means subsequent moves default to the last-used folder.