New answers tagged

0

The better option in my opinion is to have both Save and Discard buttons. If user clicks save, the popup should close and an info message saying 'Your changes have been saved' should be displayed that will fade out in 3 seconds. If user clicks Discard, show a confirmation message saying 'All changes you have made will be discarded, are you sure"? and buttons ...


0

I would go with a combo of Dipak and Toni's answers. I think the happy medium lies between. What should happen here is wholly dependent on what your users would expect to happen. This is where user testing comes in. There is really no substitute for knowing who your users are: what they think, how they feel, how they work, etc. That said, there's still ...


0

Maybe you should autosave drafts? This way the user is caught from anything that might disrupt their work, whether it's a mis-click or a power failure. As you state it's "definitely more than a couple of fields" (OP comment) you should really consider this as an option. Stack Exchange do this well, there's no cancel, just a post and if I leave and come ...


1

If you are going to ask your user a question, you should ensure the call to actions answer that question, e.g. Treat this like a conversation: "Are you sure you want to discard changes?" Yes, I want to discard changes No, I made a mistake and want to continue working This can be simplified to: Yes No Clicking Yes triggers the Discard feature and ...


4

Although users don't like to admit it, they will make mistakes. Ranging from having the wrong mental model of what a button will do to a simple misclick. It is therefor important designers take these possible mistakes into account when designing software. Two good rules of thumb are 'always ask for confirmation when a users action is irreversible' and 'try ...


2

User clicks on Save and system closes the popup? Yes. Show a feedback message on the screen behind as: Your changes are saved successfully! What if user accidentally clicks on Cancel button? Close the popup, but the feedback message on screen behind should say: Your changes are discarded. Undo The feedback messages / notification play a ...


1

There's a few other things you can do to help here. Don't put your cancel and save buttons together, that way a user is less likely to get to the dialog without meaning to. I'd put cancel over to the left out of the way, or even remove and allow the dialog close button to take that role. Autosave in the background, resulting in a 'draft' status record that ...


7

Use more specific language in your CTAs Perhaps you've got a style guide that might prohibit this, but part of the existing problem is that the microcopy is typically generic. Leave the buttons in the task modal as [Save] and [Cancel]. Restrict so that it's only possible to save from the task modal. Use more natural language instructions in the Confirm ...


0

Simplify the modal wording: "Discard the changes you made?" Make the buttons simpler as well "Yes, Discard" and "Cancel".



Top 50 recent answers are included