Open joellebel opened 8 years ago
I'm fine with this.
@kueda can you comment? I replaced the old back behavior with this cancel button largely on your request.
On the Conf. screen during the ob flow, I would make the Cancel button a Back button because it is part of a flow that people typically move back and forward through. Instagram's flow is a nice example of this.
make the Cancel button a Back button
I responded to that here. https://github.com/inaturalist/design/issues/47#issuecomment-166838114
@kueda Thoughts on this change?
Here's more of history on this issue as well, if needed (https://github.com/inaturalist/design/issues/47) ...but it's probably not necessary to read this entire issue.
This is in conflict with #134, which requests the opposite behavior, and which is why the change was made.
Sorry for not replying for the better part of a year. I am the worst. There are at least two issues here:
In efforts to move this forward I'm fine with a Cancel button as long as their is a confirmation modal like the Android app...
I don't think we need the "Edit Observation" title.
All that's left to do is add the alert about discarding changes.
When the user is in the Edit view of the Ob Detail Screen, makes changes and taps "Cancel" I recommend presenting them with a confirmation dialogue box with the following question: "Are you sure you want to discard unsaved changes? (Yes, No)
This will prevent any mistakes in saving changes.