As far as UX goes, particularly when working within the material design specifications for a Windows app, if an accept/cancel dialog is presented to the user that is intended to mutate some "model" or save some data, should the button intended to save changes only get enabled once changes have been made? (forcing them to use cancel if no changes performed)

Or is it better to have the save button enabled by default on dialog open? (disabling it if validation fails of course)

To be clear, this is a dialog, and both buttons immediately close the dialog and perform the save action.

1 Answer 1


There's an answer right in front of you.

In the field for writing questions or answers in SE, when adding an image, the Add image button is grayed out (disabled) if there's no image placed:

enter image description here

And gets enabled when there's a picture to add:

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.