Tag Info

New answers tagged

1

These comments about modal dialogs "interrupting workflow" are silly and naive. If you build your parent screen and modal dialogs as symbiotic parts of the overall task process, there is no interruption. All complex operations have to be broken down into steps or "consumable chunks of task" no matter how you build the design for simplicity. Modals work ...


0

I find it frustrating when a modal box is unmoveable, as many times the response depends on what is behind the box. E.g. if an application displays a modal "Close without saving?" box, I want to be able to move the box out of the way to look at the document behind and see if there is anything that I want to save. It's bad enough that I can't bring the ...


3

A lot of argument for making modal dialogs non-moveable centres around the fact that the need to move them stems from poor design. This is persuasive. So - if you are a perfect designer, than you can lock them in place with confidence. For the rest of designers out there, are you willing to be the one frustrating your user through some oversight of design ...


6

Modal dialogs should be movable unless you have a good reason for them to be fixed in place. Few users will ever actually move modal dialogs, so the chance of hitting any of the "dangers" mentioned are incredibly slim. But those users who do move dialogs do it for a reason, and that is usually because the dialog obscures some information they want to see ...


3

FIXED DIALOG Use for mandatory actions as it emphasizes the necessity to take that action. But, it should not hide necessary information MOVABLE DIALOG You can use movable dialog boxes unless they don't hide the information. Most websites don't use movable dialog boxes these days, as it just hinders the flow and visibility But these are just guidelines ...


43

Usually the downsides outweigh the upsides i.e. usually the answer is "no" Here are some of the typical considerations with movable modal dialogs. Note that some of these verge on implementation issues, but I've included them anyway because they all have usability impact: Moving the modal requires a lot of cognitive load. The user has to find the ...


-1

By the way you phrased the question, it seems like these actions are pretty critical to the application running smoothly. ...that command the users to take an action like log in or configure something before being able to proceed. If that's the case, then you shouldn't allow them to be moved. What's to stop the user from moving it out of the way and ...


62

I hate it when a modal dialog appears asking me to confirm an action and the only way I can confirm that, yes, this is the record I want to delete, is to view the information underneath the immovable dialog. I usually have to cancel, double check, then click again. Or, consider this scenario: Hey Mr. Team Leader, there's this case I'm working on and ...


0

Luckily not! or why would recommend not to make use of well established ui elements like tabs or floating windows? You can't really use bad implementations as reference to roll such guide-lines. Because if you would prevent tabs or floating windows, you are just adding much more inconvenience for your users. And opening real browser tabs? Really? So ...


2

IMHO, yes. See, there are 2 tendencies here: the visitor feelings about getting these dialogs "in their face" and the site owner's needs. In the first case, visitors might be annoyed, so the task of the experience designer is NOT to prevent these dialogs, but to find the proper way to compensate this perceived annoyance with a greater benefit. As a site ...



Top 50 recent answers are included