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

CTRL+Del in an open view of whiteboard deletes the file #294

Open
cb0s opened this issue Dec 2, 2024 · 3 comments
Open

CTRL+Del in an open view of whiteboard deletes the file #294

cb0s opened this issue Dec 2, 2024 · 3 comments

Comments

@cb0s
Copy link

cb0s commented Dec 2, 2024

When I have an open view of Whiteboard (v1.0.4) in my Nextcloud AIO instance (server v30.0.2) and I want to delete text with CTRL + Delete, instead of the text in the text field, the file is deleted. This leads to nasty 4xx errors.

Imo this should not happen, as file operations should not take place when editing the file. I would rather have the option of deleting entire words, as it is common in other applications.

@grnd-alt
Copy link
Member

grnd-alt commented Dec 3, 2024

Hey @cb0s thanks for reporting the issue. I could not yet reproduce in ff or chromium though, could you please share what browser/OS you're using and possibly try another browser? And to confirm, you are pressing ctrl+delete inside a text field, and the file is entirely deleted from your instance?

@cb0s
Copy link
Author

cb0s commented Dec 7, 2024

I am using FF (132.0 (64-Bit) - Snap) on Ubuntu 24.04.
Yes I am pressing Ctrl+delete inside a text field (just tested it again), and the file is deleted (put inside the trash bin). I am not sure if that helps, but the file was located inside a groupfolder.

I will test a different browser and maybe a different OS later today.

@cb0s
Copy link
Author

cb0s commented Dec 7, 2024

Ok, I was able to reproduce the same error in Chromium (v131.0.6778.85 - Snap). Weirdly enough, when I tried for the first time, nothing happened apart from a 423 Ajax error being shown as an info banner. However, after confirming the file was still present (closing the editor) and opening the file again, when trying again, I was able to observe the described behaviour - the file was deleted and I was greeted with 403 error info banners (these are also in the logs - the 423 is not). I also tested this in non-group folders with the same result.

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

No branches or pull requests

2 participants