New answers tagged

1

In an enterprise webapp we are developing we make the distinction between: modals: can only be closed through very deliberate action, because closing would break some flow or may cause data loss. These have no X button, cannot be closed by clicking outside modal. Most do have a separate "abort" button, making it more explicit that closing may result in ...


0

Answering your question, The best practice used by tech giants such as google/Facebook/twitter is giving a screen to create or edit the form. Modal might work quick but I guess form creation and editing has been on screen since ages and changing that practice might not entertain the Layman. For Layman, modal=error/information or some thing with an OK ...


1

I've got a lot of value out of putting create/edit interfaces in with the rest of the page content. Typically what I'd do is slide down the create/edit interface when the create/edit button is clicked, and slide it back up again when changes are saved. Fiddle here: https://jsfiddle.net/hr3mhufh/2/ Pros of displaying inline: No need to reload the page ...


0

What about an "edit panel" that is displayed to the right of the content? The fields in the edit panel would be automatically populated with whatever record is currently selected. I'm assuming the content is a grid / list of records to be edited.


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 ...


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".


0

It really depends on how often the data updates (and therefore how many users are working concurred) and how long the user will stay on the page. If the user logs in once per day to see, if there are new documents, the dialog showing the list of documents can be "updated" on login. If the platform is rather agile, i.e. there is lots of cooperative work on ...



Top 50 recent answers are included