[Bug]: when using search to navigate into Files, the location path is not changing

[maximelehericy]

⚠️ 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

on c.nc.c

when navigating to another location when trying to copy/move a file, the location path remains the source one instead of following the user navigation

Steps to reproduce

0. navigate to some sub subfolder in your files
1. select a few files to move
2. click the copy/move button
3. click the home icon
4. you see the location path is not changing
5. navigate to another location, the path is still not changing

Expected behavior

when navigating the files, location path should change accordingly.

Installation method

None

Nextcloud Server version

28

Operating system

None

PHP engine version

None

Web server

None

Database engine version

None

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

None

Are you using the Nextcloud Server Encryption module?

None

What user-backends are you using?

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

Configuration report

No response

List of activated Apps

No response

Nextcloud Signing status

No response

Nextcloud Logs

No response

Additional info

No response

[maximelehericy]

editing the issue, as this seems to be true not only in the copying modal, but also in the Files interface.

[maximelehericy]

it changes when I navigate clicking on subfolders to dive into the file tree. however, when using the search, if I click a folder among search results, the location path is not changing.

[sorbaugh]

odd, thanks for reporting!

[sorbaugh]

@Pytal can you take a look? I think we should get this one in for 28.0.4

[Pytal]

Cannot reproduce on stable28 or master

Does this still occur for you @maximelehericy?

[maximelehericy]

no it doesn't.

[maximelehericy]

@Pytal I can reproduce again...