Tag Info

New answers tagged

0

Removing the [X] button should be avoided at all costs since it is the go to button if you don't know what to do and want to cancel your actions. That said I have had to make a few of them in the past. The reason was that we were building a new UI on a very old piece of software. On 1 or 2 occasions the software needed a response from the user in such a way ...


3

The only time I can think of when no close button should be there is when "Cancel" action is not acceptable, e.g. the user must make a choice. This is often connected to popups that isn't caused by user action. For example, the system must be restarted and asks the user when the system should reboot. "Now", "In an hour" etc. Letting the user close that ...


1

I want to start of by saying that I loath modals. I do know that there are certainly scenarios where they are good and necessary, but I really don't like them on principal. That being said, some of the examples given, I would argue, do not justify the disabling of the close button. A close button is a very known and comfortable escape hatch. Depending on ...


0

I am more of developer than a UX person. But I feel dialog boxes without a close button have a purpose. For the most part I like a principle from About Face of don't ask for confirmation. Rather give them a chance to undo. Problem there is some actions cannot be undone and can have severe consequences. This is kind of a data integrity thing but release ...


1

Personally, I think Microsoft's guideline makes little sense. A typical dialog requesting a decision from the user give buttons for all of the possible actions to take at that point (ok/cancel, yes/no, save/don't save/cancel). On most dialogs, the close button doesn't give the user additional "control"; it just provides a duplicate way to perform an ...



Top 50 recent answers are included