[Bug]: Client 3.9.0 problems when renaming files in Nextcloud directory using W11 Explorer

Sergeij2000 commented 1 year ago

⚠️ Before submitting, please verify the following: ⚠️

[X] This is a bug, not a question or a configuration issue.
[X] This issue is not already reported on Github (I've searched it).
[X] Nextcloud Server and Desktop Client are up to date. See Server Maintenance and Release Schedule and Desktop Releases for supported versions.
[X] I agree to follow Nextcloud's Code of Conduct

Bug description

When trying to rename a file in the NC directory, the cursor jumps back to the beginning of the line after 1 or 2 seconds and the whole filename excluding the extension is again highlighted. After downgrade to NC client 3.8.2 the problem was gone. After upgrading again to NC client 3.9.0, the problem was back again, but slightly different: The filename was not highlighted anymore, only the cursor jumped back to the beginning of the filename after 1 or 2 seconds.

Steps to reproduce

Open the NC directory in W11 explorer
Select a filename and enter Edit-Mode (slow double click or F2)
Try to move the cursor into the middle of the filename for renaming a portion of the text ...

Expected behavior

When selecting a filename in NC directory for renaming and moving the cursor into the existing text, the cursor position shouldn't jump back to the beginning of the filename.

Which files are affected by this bug

Only files in the NC directory

Operating system

Windows

Which version of the operating system you are running.

Windows 11

Package

Official SNAP package

Nextcloud Server version

25.0.7

Nextcloud Desktop Client version

3.9.0

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

Updated from a minor version (ex. 3.4.2 to 3.4.4)

Are you using the Nextcloud Server Encryption module?

Encryption is Disabled

Are you using an external user-backend?

[ ] Default internal user-backend
[ ] LDAP/ Active Directory
[ ] SSO - SAML
[ ] Other

Nextcloud Server logs

No response

Additional info

No response

joshtrichards commented 3 months ago

Hi @Sergeij2000 - I haven't run across this before. Are you still experiencing this with newer versions of the client? Any chance you've reproduced it on more than one computer?

sharcslife commented 3 months ago

I had this issue with one of our devices sometime earlier this year, I guess with Windows client 3.12.6 whilst using the virtual files sync-method. We switched the device to the traditional sync method and it was fine then. Not sure if that was actually the issue though, as it had worked before and also worked and works with other devices using the same software and methods.

nextcloud / desktop