Consider an Angular app with many user inputs over screens A, B and C. Screen C needs valid inputs from A and B; B from A only; and A is independent. Suppose while on screen B the user enters invalid inputs.   Question: What  navigation should I support for B in this case?   My current thinking is to disallow navigation to C due to data validity issues. But what about navigating back to B? On the one hand, there are no validity issues, and the user may want to look up screen A to help with screen B inputs. On the other hand, this would complicate the app's state management. An alternative is to disallow such navigation, possibly with an option to restore the last valid inputs at B.  As I lack experience in UX, I'd appreciate answers to help me with this trade-off.
121667
Scenario:   User makes a series of entries in text fields on a page that requires apply/cancel buttons. Invalid entries are flagged with an error icon and hover-over tooltips that explain the validation error.  The "apply" button remains disabled until all fields are valid; users cannot apply invalid entries BUT the user is still able to navigate away to another page of the software, at which point they receive a dirty flag notification: "You have changed some settings blah blah, would you like to apply them before leaving this page? (Apply/Don't Apply/Cancel)"   Problem:   How do we handle the case where the user clicks "Apply" in the dirty flag dialog while they still have invalid entries?    Considered solutions:    After they click "apply", they receive an error dialog stating "Some settings are invalid, could not apply" and the invalid entries are rejected, reverting the fields to their previously saved states. After user closes error dialog, they move to their destination page. We include a message in the dirty flag dialog along the lines of "Only valid entries will be applied, invalid entries will be reverted to last state." When the user clicks "apply" in the dialog, they move to the destination page and only valid entries are applied Before the dirty flag dialog even appears, the user receives a notification dialog stating "Some entries are invalid, please fix before continuing." They fix the invalid fields and try to leave the page again, at which point they encounter the dirty flag dialog.    We're in a conundrum about which solution is the most elegant. This whole situation is awkward to begin with, considering the few cases where a user would try to leave a page without applying their changes... But yeah, which of these, or others, would best be the most appropriate solution for us?
8823
Following are other questions which I think I need to know:   From a non X Session? (meaning root isn't logged into X) If multiple people were logged in on X, could I auto-detect who was on which screen, and thus programmatically detect which screen I need to launch the app on? Can I launch the app as the user? ( ok I'm 99.999% sure this is a yes ) Can I detect if users of group X are logged in to X?
114337
Similar question here:   However, I want always-use-location-entry to be true. So I am not using breadcrumbs.  The shortkeys, both Backspace and AltUp, are quite helpful. However, since I'm mainly using my mouse in Nautilus, I'd much prefer to actually have a button present that I can click. Then I don't have to switch between keyboard and mouse all the time.  Is there a way to add this button/functionality, while keeping always-use-location-entry to be true?  Another workable solution would be to use both breadcrumbs and the location-entry; so a parent is clickable, but I can also type a path directly.
14133
Android 7.0 introduced the native multi-window API which allows apps to be viewed in split-screen mode globally.  However, in actual usage, one downside prevents it from being as useful as some users would imagine. Many apps, when in the multi-window view but not in focus (i.e. user is interacting with another app in the multi-window view), pauses its activities: IM apps would no longer update incoming messages; music/video apps would pause playback; games would not proceed with their actions.  The official developer guideline  the pausing behavior, and from what I understand, apps need to be programmed with this in mind so as to not exhibit it. But is there a way I can force the way around the limitation as a user? From what I've heard from fellow users, certain manufacturers' Android forks such as MIUI do not show such pausing whatsoever.  TL;DR: Can I prevent the out-of-focus app from pausing in multi-window?
20241
In usability discussions about opening website external links in new windows, with regard to the argument of "keeping users on the site" there are occasionally references to usability studies which show that users are actually likely to leave the origin site instead of returning (thus defeating the purpose of opening the link in a new window).  But I can't find actual recent published studies on this, and I've searched extensively. Though Jakob Nielson is reputed to be a foremost expert, his recommendations are old and have no citations that I can find.  Does anyone know of credible, recent, published usability studies where users were disoriented by new windows and were more likely to not return to the origin site?  Update:   I understand there are accessibility issues, but as those matters are well-documented and backed up by the WCAG, I'm not in need of evidence supporting them.  This question is intentionally specific to the argument of "I want to keep users on my site" because it is the argument which -- due to lack of supporting evidence -- I can't effectively counter in discussions with the client.  Update:  Found this . Haven't fully deciphered it, but the thesis does claim that new windows / tabs increase the cognitive burden on users.
63063
OK, here's the situation: A reasonably simple website with a primary navigation menu including drop-down list of sublevels on hover. Each navigation level may have 3 - 6 sublevels below it, none more important than the other. For example see this mockup:    My question is: What should happen if the user Clicks on one of the primary navigation options (such as 'News') instead of just hovering over and choosing a sublevel?  My instinct tells me that I should allow a click of this navigation option; it's expected user behavior to be able to click navigation options. If clicked then a landing page of some sort will be present listing all the sublevels (latest news, blog posts, case studies'). However there is no content to add to this landing page other than presenting a list of links, which is pretty useless. I could pad it out by adding iconography and descriptions of the sublevels, but that's just content for the sake of it; does 'Latest News' really need a description in order to understand what it is?  If I don't include a landing page then clicking this primary navigation will have to open something but if I open the 'Latest News' page that risks the user not knowing about the other sections of the site.  (The landing page will be useful for breadcrumb navigation too, so I don't really want to do away with it).  Is my thinking that a landing page showing the list of sublevels actually useful even though there is no actual content to display, or is there a better alternative to go with?
86684
A user of ours cleared their path, thanks to some directions on the internet.  What is the default path, I am a developer so I have tons of extra stuff in mine, what should my user get on a plain jane one?
62642
Topic of discussion.  Is it a usability problem to have an input field be too wide?  For example:  I am creating an internal management system where users come to view orders in the system. When viewing the orders users can enter in comments. To make data entry easier I have made the decision to have the input fields already appear at the top of the page so the user just has to start typing and enter data at a faster speed.  With this being an internal app we are utilizing the full width of the screen so the "notes" input field spans the full width.  Should this be a usability concern?
18522
If I want the user to revert their operation of selecting an item, should I say: "Unselect the option" or "Deselect the option"?
671
So the SMEs at my current place of employment want to try and disable the back button for certain pages.  We have a page where the user makes some selections and submits them to be processed.  In some instances they have to enter a comment on another page.    What the users have figured out is that they don't have to enter a comment if they submit the information and go to the page with the comment and then hit the back button to return to the previous page.    I know there are several different solutions to this (and many of them are far more elegant then disabling the back button), but this is what I'm left with.  Is it possible to prevent someone from going back to the previous page through altering the behavior of the back button.  (like a submit -> return false sorta thing).    Due to double posting information I can't have it return to the previous page and then move to the current one.  I can only have it not direct away from the current page.  I Googled it, but I only saw posts saying that it will always return to the previous page.  I was hoping that someone has some mad kung foo js skills that can make this possible.  I understand that everyone says this is a bad idea, and I agree, but sometimes you just have to do what you're told.
27344
I've noticed that most people when using a real or a virtual calculator, they hit the Clear button multiple times when clearing the screen (even though hitting it once is enough), so I started wondering: is there a flaw in the calculator's design that compels most people to do that?  What makes them trust the button less than the other buttons? Is there some sort of feedback mechanism that's missing? Even if it's just a habit, how does one end up developing it?
81145
Quite a while ago we decided to move our hamburger menu (I know they are evil but we got stupid amount of subcategories) to the right. Reasoning behind that was based on accessibility and in indoors labs it proven that people preferred it this way.   Now we are doing some reworks regarding mobile top banner and search. While doing research I noticed that literally all of our competitor has their hamburger menus on the left.   Is it worth sacrificing usability (way easier to reach menu) for consistency (everyone one else is having their hamburger menus on the left).  It is worth noting that our customer base is heavily using mobile devices especially iPhones.  There is similar topic but I dont think it covers particular use of hamburger menu location on websites, and not apps.
106265
One thing that irks me is redundant controls. For example, there was a game I used to play that had a "disable IP check" option, but if you enabled it without Game Operator permission then you would be permanently banned. I have no idea why they couldn't just give the GO that option instead of giving people a "ban me now" button...  Anyway, back to SO. Since a user cannot vote on their own questions or answers, what is the point of the arrows being there? It seems wasteful to have buttons that I cannot use (and it's annoying when I accidentally click them when trying to expand my vote score, but that's probably just me), and I think they should be removed.
113421
i have a visualforce page where i displays a grid with checkbox selection for each row in it. The issue is when i select the checkboxes in page 1 and navigate to page 2 and comes back to page 1, the checkbox selection disappears(unchecked) in page 1. i need to retain and display the checkbox selections while i moving across the pages back and forth. How can i fix this? please help.
55169
I built a site with Angular 10. When the home page is visited it reroutes to this /welcome. However There's no link to that from anywhere within the app, so I don't think Google has any way of indexing that page. What would be the best way of telling Google to index the page.  From my research it seems I could do something like this: &lt;body&gt;   &lt;a class=&quot;hidden&quot; href=&quot;/welcome&quot; title=&quot;Welcome to example.com&quot;&gt;Welcome to Example!&lt;/a&gt;   &lt;app-root&gt;&lt;/app-root&gt; &lt;/body&gt;  What is the max number of links that this would work with and any other approaches?
20457
In 2008, :     A long time ago, it became fashionable, even recommended, to disable   menu items when they could not be used.      Don't do this. Users see the disabled menu item that they want to   click on, and are left entirely without a clue of what they are   supposed to do to get the menu item to work.      Instead, leave the menu item enabled. If there's some reason you can't   complete the action, the menu item can display a message telling the   user why.   That's an interesting idea, but I wish he'd elaborated on what he meant by "display a message telling the user why."   Has anyone actually followed this advice? Are there any examples of menus that display a message instead of disabling a menu item -- perhaps something you designed yourself, or something out of Fog Creek?  I'm curious about the mechanism by which the message would be displayed and whether anyone has experience (good or bad) with showing a message instead of disabling a menu item.
123005
Steps to reproduce:   In your feed, tap an item that references a deleted post.  In this case, it tapped a comment reply on an answer I deleted. Observe that the question loads, but scrolling on the view is disabled. Tap the down arrow on the right side of the navigation bar. Observe that the screen scrolls down to the first answer, and then scrolls back up to the question. Observe scrolling is enabled again.   Expected result:  Navigating to a question from a reference to a deleted answer should not break scrolling on the question view controller.   App Version: 1.6.1.2 Device: iPhone 6 OS Version: Version 9.3.4 (Build 13G35)