[Bug]: cropping an image leads to multiple errors and undesired outcome
Open
Nobody has claimed this yet.
0. Needs triage
bug
- Dominant language
- JavaScript
- Stars
- 119
- Forks
- 72
- Avg merge
- 18h 42m
- Merged PRs (30d)
- 24
Description
⚠️ 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.
Steps to reproduce
I did this on c nc com:
- in files, click on an image
- resize it
- try to overwrite it (save with the same name as original)- button confirming that I want to overwrite has wrong color, text hard to read - I heard a fix for this is underway
- saving failed
- then I tried again with a different file name, again an error
- back in files list: where is the image I just worked with? is it necessary to reload the page to see the file?
- after reload I see that actually both files were written but in very low quality, I don't think I told the editor to downsize quality?
- all very confusing
Expected behavior
- it works, no errors
- file should be visible in file list immediately after the editor closes, no reload necessary
- file has same quality as original file
Nextcloud Server version
34 (master)
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
List of activated Apps
Nextcloud Signing status
Nextcloud Logs
Additional info
No response
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the image resize and save flow in the Nextcloud Files viewer, testing both overwriting the original and saving under a new name. Check the reported save errors, file-list refresh behavior, overwrite confirmation styling, and resulting image quality; done means both saves succeed, the file appears without reloading, and quality is preserved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100