Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Reload of browser after rename operation completes discards current editing state #11639

Open
cyberduck opened this issue Mar 31, 2021 · 4 comments
Open

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Mar 31, 2021

6856d9b created the issue

  1. Rename a file
  2. Before step 1 finishes, start renaming a second file
  3. After step 1 finishes, the rename session started in step 2 is ended
    Expected: I should be able to continue renaming as desired
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 1, 2021

3cbfc3c commented

Hi,

Thanks for reaching out. [[br]]
Please update to the latest released version of Cyberduck (7.8.5). If the issue persists please tell us the operating system and the protocol that's in use.

– Sofie

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 1, 2021

6856d9b commented

Still happens on 7.8.5. macOS 11.2.3 + S3.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Apr 7, 2021

3cbfc3c commented

Is reproducible but currently expected behavior.

Loading

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented May 13, 2021

6856d9b commented

If you're renaming many files quickly, then this bug means that files will have the wrong name. It is not useful/expected to end (and save!) an in-progress rename session just because another rename completed. Since this causes loss of user data during a common operation, I increased the severity.

Loading

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
1 participant