I think Steam just haven't noticed this problem.
Here are some reasons to put the logout button at the bottom of the dropdown:
Avoid Accidental logouts - as you pointed out putting the logout at the top of the list could create accidental logouts for users that are used to double clicking on elements.
Follow standards - when browsing the internet users ...
Make it harder to find destructive buttons
If you do need to include destructive buttons, you should definitely
find a way to make them harder to find than the primary action button
Best practices for buttons
It's very important for businesses today to keep the users engaged with their products, and no one wants to give them an easy access to the ...
I don't like tree views, but sometimes they really are the most appropriate widget.
Before you write the tree view off, it's worth thinking about whether it can be redesigned better for tablets.
1. Issues with tree views
The drop-down icons are usually too small. They're hard to click even on desktops, let alone on tablets (see Fitt's law).
Idea Can we ...
Think about each menu item as a task. You can perform tasks sequentially, like task1, task2, task3.... taskN . Which would be the very last task you can perform? Answer is easy: logout.
By adding the logout link at the bottom of the menu, you make it harder to accidentally click that element. See graphic below:
Once you open the ...
You're on the wrong path, here.
The problem is that you try to show the attributes in different trees.
The tree should contain the content.
The attributes should be displayed as attributes to each node.
This can be done in various ways depending on the importance of attribute.
As a column:
- As a popup dialog
- By showing the attributes directly ...
Anything is commonly considered organized when it looks like
everything has a correct order or placement. But it's only ultimately
organized if any element has no difference on time taken to find it.
In that sense, organizing can also be defined as to place different
objects in logical arrangement for better searching.
Luke Wroblewski has done a lot of research on web forms.This article on dependent dropdowns would probably answer this question more fully for you.
He breaks selection dependency into a few different visual displays: page display, tabs (section and finger), section selectors, and exposing with radio buttons (below, within, inactive, and groups).
Consider panels that come out from underneath each other to reflect the hierarchy in dimensions. The top is some major classification that you can still trace back. As you go deeper into the hierarchy previous panels slip off to the left. You can go back up the tree by swiping them back to the right.
When you finally hit on an option that has no more ...
I have not seen this pattern employed exactly as you describe. My relevant experience in information-rich webapps stems from enterprise health-monitoring and deployment software, which has a deep navigation hierarchy.
In my opinion, the left-navigation and the main content should not both employ accordions.
Left hand navigation is typically vertical, and as ...
When designing for presentation of information, it is important to try and fit the interface as closely to the underlying data structure and the relationships between the different sets of data as possible. In general the aim is to make the relationships as simple as possible, and it might mean also using a combination of data structures if it makes sense to ...
Microsoft have left the TreeView display in mind when they introduced Windows 8. Now you move down the hierarchy by clicking items (categories) and using the back button to brows back. This is the default style of hierarchical navigation on Windows 8.
So a TreeView control in the style of Windows 7 and previous Windows versions does not apply. Take the ...
You can use background color to represent going deeper in the hierarchy and avoid using too much indentation.
If you do not want to color the entire background of the post, you can do just highlighting the edge with a color.
In any case, I would still have the tiniest amount of indenting because it is a much stronger visual cue. You can compensate the ...
Another option is to use Miller columns, which is essentially a treeview flipped around and structured in rows.
This is a rather common approach in file organizers, but you may find it a little bit tricky when there are too many levels of hierarchy.
You could also look at an organisational chart or graph that is commonly used to represent hierarchy within ...
To my understanding, the log out button is the button in the dropdown that has a different action than the rest.
The rest of your menu account details, preferences, view profile etc are navigation elements for the user, but the log out button is an action that would make the user log out from the system.
What is sure is that the Log out and the ...
Remove the chrome. People don't like living in houses with scaffolding. Similarly, it's hard to read an expression where everything is surrounded by a box and has several buttons attached.
Generally you want to start by asking "What is the most understandable format that I can write this expression in?" Use a whiteboard, and imagine you're trying to explain ...
I don't see a big difference in difficulty of implementation between the two models you describe but this ins't an implementation discussion.
Only people with much more information about the project can determine whether the extra cost of implementation to achieve greater usability will pay off. My initial reaction (and that of most people here I think) ...
Yes tags can be hierarchical and there is actually a lot of (not yet widely recognised) potential in it.
Although some people (probably like the question asker) have been curious and/or after hierarchical tagging for years, the reason it is not present on the CMS market now is more because of technical obstacles rather than not seeing point in it. With pure ...
I have a similar set up for a test environment and a production environment.
I found myself accidentally adding test data to the live database. So I wanted to make sure that it was easy to identify which server I was on. I could glance at the address bar, but it was too easy to forget. I wanted the differences to be minimal but obvious.
I chose to add a ...
Some improvements are:
Remove agressive black border as it takes too much attention
Use single grid, it creates simple visual structure
Align numbers to the right for easy scanning and reading
Remove repetitive 'Score'. It breaks the numbers reading
Don't use too long empty lines
Be careful with zebra-coloring the lines, as printed version could be hard ...
This a common case in a complex workflow or process, which can be solved with progressive disclosure, like:-
Initially show all parent tasks with their progress indicated and also childs status with notation like 2 off 5 childs is comleleted (indicated by showing 2/5).
For more detail user can always expand a parent task to get sub-task details which in ...
Personally, I think your main issue is to use a table, which complicates things and provides an affordance that collides with what you want to achieve. Think about this: I see your categories list, and see there are 10 per page. Great. Now, I expand your category... and now I see subcategories but some of the categories I was seeing disappeared! This is a ...
It sounds like you're offering an affordance that the users would benefit from, but you're explaining it in the terms that make sense to you. Rather than using the concepts of propagation and hierarchy, I'd set it up to use the more familiar "apply to everything like this" pattern, which commonly shows up in applications and OS functions.
Your presentation ...
This is a common pattern for users.
If a subset of child items are selected, the parent item indicates partial selection.
If the parent item is clicked while in the "partial" state, all child items will also be selected.
If the parent is deselected, all child items will be deselected.
I think the problem here is you shouldn't use a table, but something different. The first easy choice is a Tree View. Tree view is a system that allows you to organize hierarchical data in an easy to understand manner, and most users (if not all) know how to use it and its affordances.
From an implementation side and user experience, it also allows you to ...
Showing multiple prices should not be an option.
You can think a lot of reasons for that, like misunderstanding of users, perception of users, possible longer lists for countries which will be added in the future etc...
So, you should show just one price, which leads us to another question: which price?
You can find many answers for this another question ...
"The Problem: On one hand deeply nested code is hard to read. On the other hand, visualising nesting levels are necessary to understand code. De-nesting code/html requires a lot of effort, which only improves readability, not actual code effectiveness, accuracy etc."
Do you know that 'de-nesting' improves readability for sure i.e. you or others ...