(In reply to Geoff Lankow (:darktrojan) from comment #4) > Because in the case of CardDAV at least, that would require a trip to the server for every field that is changed. If frequency of saving is a problem, you could still wait and silently save the whole contact (without prompt) when one of the situations from comment 0 arises. Which is still silent (prompt-less) saving, only not instant. > And also in the case of a new contact, there is nothing to update, it doesn't exist yet. That's a technicality which is easy to solve, so instead of updating, it becomes creating the contact. (In reply to Magnus Melin [:mkmelin] from comment #5) > Typically editing contacts does require an explicit save: see phones, or on the web, google contacts do not autosave but require explicit save. Good point. And how many times do users lose their new contacts because they forgot to tap `Save`? Happens all the time imo... I don't have a strong opinion on this, but we might want to explore new and potentially better behaviours freely. Maybe someone could point out the workflow benefits of prompting for contact changes (especially for *new* contacts, but also existing)? Is it about unfinished contacts or accidental changes?
Bug 1734298 Comment 6 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
(In reply to Geoff Lankow (:darktrojan) from comment #4) > Because in the case of CardDAV at least, that would require a trip to the server for every field that is changed. If frequency of saving is a problem, you could still wait and silently save the whole contact (without prompt) when one of the situations from comment 0 arises. Which is still silent (prompt-less) saving, only not instant. > And also in the case of a new contact, there is nothing to update, it doesn't exist yet. That's a technicality which is easy to solve, so instead of updating, it becomes creating the contact. (In reply to Magnus Melin [:mkmelin] from comment #5) > Typically editing contacts does require an explicit save: see phones, or on the web, google contacts do not autosave but require explicit save. Good point. And how many times do users lose their new contacts because they forgot to tap `Save`? Happens all the time imo... I don't have a strong opinion on this, but we might want to explore new and potentially better behaviours freely. Maybe someone could point out the workflow benefits of prompting for contact changes (especially for *new* contacts, but also existing)? Is it about unfinished contacts and/or accidental changes?