I've been given the following design for an error modal dialog (the rest of the page is grayed out and can't be clicked):    To me, instinctively, it seems redundant having two ways (close button and ok button) to do the same thing (close the dialog).  I don't see the need to have the close button.  Can you provide some more solid reasons to avoid that, or good reasons to have both if I am wrong?
31322
I am working with a basic  which is a popular modal used on many sites. I noticed that the default template comes with both a close button on the bottom, as well as an x on the top, these two buttons essentially having the same purpose. Are the two redundant and the close button completely unnecessary and just taking up extra space? Or, is having multiple usage options more user friendly?   To make this even more fun, suppose I throw in a Save button:   Is it now clearer that if you don't press save and just press the x, your changes will be canceled, or is there now more of a need for a cancel button for users who are scared that a mistake will become permanent? Update: To clarify for those who feel this question is similar to  - That question is asking if a clickable background is sufficient to close a popup. I'm using buttons and it is just a matter of how many buttons to use. (I do also have a clickable overlay and ESC key enabled, but that is irrelevant to my question)
116918
When using divs when is it best to use a class vs id?   Is it best to use class, on say font variant or elements within the html? Then use id for the structure/containers?   This is something I've always been a little uncertain on, any help would  be great.
44307
Possible Duplicate:             When I select Off topic option in Vote to close it shows only few options. I know that this question belong to .   How can I select that option to tell the OP to ask there?  The close window shows the below options:   Meta Stack Overflow  Server Fault  Super User Tex Stack Exchange DBA Stack Exchange   How to add other option?
61488
Designing an interface for a CMS (Content Management System), I stumbled upon a paradox and I'm a bit confused about what to do and why to do it..  Context  Before deleting an album, the user is asked to confirm the action.  Green "Yes"    Red "Yes"    Which option is more intuitive for the user?
81314
I've noticed a lot of news websites, particularly on mobile, sometimes will cut off their story with a button you have to click to see the rest of it. I can understand why they'd do this if they wanted to make you pay for the rest of the article or shove an ad in your face, but sometimes the button just shows the story and does nothing else.   .    To me, this seems like a really bad user experience. Making someone tap a button to continue browsing your site seems like a good way to lose their interest. Is there some hidden value in this interface design choice? Or does it serve some unrelated purpose (perhaps for analytics on user engagement?)
47940
How do you think about disabling the submit-button until the user has completed the form or the required fields?   I find similar questions here on ux.se and somebody answered that the user will think that the form is broken or not immediately realize whats going on.  I think hiding is not that good but a disabling (e.g. grayscale, opacity, ...) plus a short text in the button would improve usability because the user realise that he still has to fill out something.  Is there anybody with experience or examples besides the usual error-messages/validation after submitting?
66339
How many times did you use a desktop app or an online page and you come across one or more menu items which are disabled and you have no idea why its disabled. Using help or documentation is of no use. It gets frustrating because it's stopping you from moving forward.  I have NEVER seen this usability practice used. Hover over the disabled item and a tooltip lists you the reasons and you go "Oh.. ok. now I know". Your other option is you have to contact support or post in a forum, explain what you were doing. Wait for what possibly be days tell you get an answer, if any. This is the difference between black &amp; white. Getting instant help by a simple hover or get frustrated and wait for hours.   If you are the one developing the app, you know exactly why an item is disabled because you disabled it in your code. So it's not hard to show the reasons to the user. Is it?  This little tip could have saved thousands of tech support calls. There are millions of posts on the web of Why something is disabled or grayed out.
37788
I've noticed and used the new (at least for me) button Leave Open, but I can't find any explanation as to the implication of clicking it.  I've found a highly voted  question:       ...How about, as soon as there's one vote to close, there should be an option to counter the close vote, something like "vote not to close" or whatever. This would then bring the "Vote to close" number down by one.   Is this that is happening? Or something else?    By reading the FAQ, there's no mention to this new action... so I'm assuming that an update is coming to the last paragraph of :     Users with 3000 reputation can cast up to 50 close votes per day. When a question reaches 5 close votes, it is marked as closed, and will no longer accept answers. Closed questions may be opened by casting reopen votes in the same manner. However, you may only vote to close or reopen a question once.
89204
When reviewing on SO, I accidentally pushed the "Leave Open" button on a post that clearly should've been closed. I pushed the back button and saw that in the review panel my vote to keep open had been locked and it said:     PhpMyCoder voted to leave open 1 minute ago   So I clicked on the question heading to go to its page and I clicked the close link on the question page and voted to close for the relevant reason. However, when I returned to the review page (and did a hard refresh) it still said:     PhpMyCoder voted to leave open 2 minutes ago   Is it possible to vote to leave open and vote to close at the same time? I assume not. In which case, I'd say this is a bug because it should've updated to say:     OtherUser and PhpMyCoder voted to close 2 minutes ago
56044
It appears that the recent UI change for the close vote review dialog introduced a bug when it concerns suggested dupes. Reproducing in Firefox 78.0.1 (Mac OS). In this dialog there are two tabs, &quot;Question&quot; that shows the question to be closed, and &quot;Duplicate&quot; that shows the suggested duplicate. When the latter tab is active, the &quot;Close&quot; button produces no action though it is not disabled.  Only when on the &quot;Question&quot; tab can you successfully vote to close the question.   There seems to be an uncaught exception raised by JQuery, when called from review.en.js:  SyntaxError: Document.querySelectorAll: '.close-question-link[data-questionid=63380604]' is not a valid selector  Looks like the original question ID may be lost when switching to the &quot;Duplicate&quot; tab.
46698
My project has a table with '+add' button and filtering. The add button opens a dialog to add item, and then to 'save' which closes it too Today I noticed the following flow:  Filter table on subject with value 'dummySubject'  Add new item with subject 'somethingelse'  save and close the new item ==&gt; the new item is shown in the table   So the outcome is that an item that does not qualify the filtering appears in the table. When I asked around I got the following answer  We don't want the new item to 'disappear' on creation just because it does not qualify the filtering. So we display it If you filter again, it will disappear as it should  I can almost understand that logic, but still it sounds wrong. I would rather have like a toaster saying 'new item create' with a 'goto' link. My question is  is the current user experience considered a reasonable one? what is the best practice way to handle such scenario?      &ndash; Wireframes created with
49689
As everyone is becoming aware, the .  When voting to close a question, the first dialog is nicely laid out and easy to look at:    But the dialog containing the off-topic reasons is considerably harder to read and assimilate due to its layout and the fonts/weighting used. It's almost a wall of text:    When you've changed things, you want to make it easy for people to follow the new process. You don't want them to struggle to work out what the appropriate reason should be.    Can we have this re-jiggered to match the style used in the first close dialog?
112612
I hope this is the right place to ask this question.   and it was almost immediately closed by a moderator with the reason     Closed this as the only two possible answers are "yes it is" or "no it isn't".   I'm a long time SO user and I didn't remember this rule, so I searched here:       But in none of these threads was I able to find a rule that explains the reason why the question was closed.  Can you help me to understand?  What I can't understand, is that if I had opened the question with no context, then people would probably have asked me "what have you tried"? I added my context, and the question was closed because it's only a yes/no.  Moreover, this statement is not correct. In fact, an answer to a yes/no question can contain several additional details, as you can see from the comments. People are suggesting improvements and alternatives.
72270
Sometimes when in the middle of writing a custom moderator flag, I click outside the flag dialog, for example because I want to get a link to one of the answers. This closes the flag dialog and forces me to write my message all over again, which is rather annoying. Therefore, I propose that clicking outside the flag dialog don't close it when I'm in the middle of typing something in a textbox (a&nbsp;custom moderator flag, a custom close reason, etc.).
44421
What happened to the close vote option for posts that describe an error or unexpected result but don't include the relevant code or any code!? This is on of the two most popular I use.. What am I supposed to do about questions like  now!?  I just also noticed "must show minimal understanding" is missing as well. After reading over the new option again, I am supposing that the intention is to use "not likely to be helpful for future viewers" for both of these?
114028
I came across  today. In reading the answer and the comments it turns out that the issue was just a simple typo that the OP made. So that being the case I decided that this question probably needs to be closed since this will not be helpful to any future vistors. However, in looking at the flag reasons (I don't have the close ability yet), I don't see a flag that would be appropriate.   I know some of these options might still be influx because of the . However, until a different off-topic flag description is created, how should this be flagged? Or should this not be flagged at all and just allowed to live on or wait for a user with close votes to use a custom off-topic close option?
122236
I remember once reading an article that said whenever you present a messagebox with a Yes/No choice, you should always also provide a Cancel button, even if it does the same as No.  The rationale was that if the users know that Cancel is always the "safe" button to click if they don't understand why the message box was displayed, or are confused by the question.           &ndash; Wireframes created with   I've followed this advice for years (even though I can no longer remember where I originally heard it), but a number of people have complained about it, saying that they would prefer a simple Yes/No.   So now I am wondering whether it is (or ever was) in fact best practice. If a message box presents a Yes/No choice, should it also offer Cancel (in the case where Cancel and No have the same effect)?