nextcloud / nextcloud/contacts
Hitting the save button too quickly doesn't save the changes
Open
Nobody has claimed this yet.
2. developing
bug
feature: contacts
- Dominant language
- JavaScript
- Stars
- 642
- Forks
- 220
- Avg merge
- 14h 39m
- Merged PRs (30d)
- 51
Description
Describe the bug
When editing a contact, changes are not saved when the save button is pushed too quickly.
Steps to reproduce
- Open an existing contact.
- Edit a field (e.g. phone number).
- Hit "Save" instantly (be fast!).
- Reload the page.
Expected behavior
The field reflects the edit.
Actual behavior
The edited field has the original state before the edits.
https://github.com/user-attachments/assets/8eff0695-65e8-4834-8c9c-7e90901e06e4
Contact version
7.3.10 and latest master
Operating system
No response
PHP engine version
None
Web server
None
Database
None
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
No files or tests are named. Start by reproducing the issue in the contact editor: change a field and immediately use Save, then reload to confirm whether the edit persisted. Done means an immediate save preserves the changed field, with regression coverage for this interaction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100