Tag Info

Hot answers tagged

11

Apple removed scrollbars from appearing, unless in use, from viewports in 2011 with the release of Lion, immediately sparking multiple articles about how to get them back. The usability rationale and merit of this can still be debated today. Not showing it until it is needed is a clean design and does not clutter the display, but the user must figure out ...


3

Though I couldn't find any research data about whether people use the scroll bar or not,other than enabling users to scroll down the page, scroll bars also provide a visual affordance to users that additional content is present below which they must scroll to see. If you hide your scrollbar, users might be aware of the additional content and may not scroll ...


3

Oh no, not this again. Users scroll. I've always had this discussion with people when they ask: "If we hide information underneath the fold, will they know that there is something there?" What is the first thing that people do when they land on a page? They try to discover, and one way they do that is by scrolling. If a user cannot scroll, the page will ...


3

The answer to your primary question is: no, you should not force or emulate a scroll bar on mobile devices. Explanation Mobile platforms already have a scroll bar in the interface. However, it becomes visible only when a user is scrolling. If you introduce an element that nobody else is using, you are creating an expectation for users to see this element ...


3

The scrollbar has several important benefits. The height of the scrollbar relative to the window corresponds to the height of the visible content relative to that of the full content. This provides an at-a-glance sense of scope and orientation. In addition, the mere existence of the scrollbar indicates that content is hidden, and communicates the direction ...


3

First, I would definitely not go with option #4 for the reason you outlined. I have to ask, without being able to see exactly what you are talking about, is there a reason it's a problem that the content doesn't fit within the fold of the page? Is there a lot of content and it would just stretch the page too much? Out of the choices, mine would be #2. That ...


2

It was designed for the majority (pareto) use case With generic scrolled content, it's more typical to read the content page by page than to jump directly to a location. Therefore, the scroll track was designed as a large click zone for paging down through content, since that was the more common use case. Note that in practice this is inconsistently ...


1

It can work but it has some issues ...so make sure there is a tutorial or a label to show the user how this works. For example, if the user hovers over the yellow part, you might include a tooltip that says Jump to code example C, for example. Note that a similar approach is used in browser and other apps...here is how the Chrome browser handles finding ...


1

I think this would really need user tests. Without that information and if I understand correctly I would opt for: A- Most users use the notification panel and don't frequently click on show more or they just do it a few times (let's say 2/3) By default scrollBar just for the main page. By default show some limit amount of notifications. If the user ...


1

This is not a "feature", it's bad (or unfortunate) design, and there are two reasons for it, and one it technical: The height of either content in the modal or the content of the page is higher than the designer anticipated. The technical cost of setting a proper height of the modal was considered too high (and in unfortunate circumstances near ...


1

Mobile UI nowadays uses the accelerated scroll method. The faster you scroll up or down the faster the content moves up or down. It therefore becomes very easy for users to reach the bottom or top of the page easily. If the page is for reading content where I'm not wanting to get to one end or the other very quickly, I would suggest a scroll bar of some ...


1

Scrollbars provide three real benefits: 1. Scrolling Although this was their initial primary purpose, it was also never the only way to scroll, as users could use page up / page down or spacebar / shift + spacebar. it has largely become obsolete for users with mouse wheels, or some touch scrolling. 2. Position Scrollbars give an indication of where in ...


1

It's personal. I've seen websites employ menu elements (top level) that are invisible until the mouse goes over the menu element. I would suggest that is an example of bad UI, as the relationship to the menu element and the mouse is required and a relationship between the user and the menu element is required for the user to make a decision as to what menu ...


1

In my experience of usability testing — most people still use the scroll bars. Including Mac users.


1

An opinion from the other side: Oh my word I love this behaviour. I have moved to a Mac for work and I miss it dearly. When you're working on or reading a document or webpage, you can grab the bar scroll up or down to check something, and then drop it again to continue from where you were. As has been said here already, it's about cancelling an operation ...


1

Most websites seem so make use of the words "back" and "top" most of the times (see this list for examples) in various combinations (back to top, back to the top, to top, top,...). I do not completely understand what you mean with it not being "classy" enough. What is your definition of classy and which analysis shows that users find it insufficiently ...


1

I use an up-arrow and the word "Top". Regular Hovered Here is why I use it: It is intuitive - Everyone knows where it's going It is clear - Don't have to worry about ambiguous wording like 'Back to Top' It is simple - Minimal wording to reduce crowding of the button.


1

What do you think about to create overlay bottom bar with the context buttons? Update: Just to explain the color scheme behind the screen: Green button is 'Save', red button is 'Cancel', blue button is in this case used to check not assigned entries. This is just concrete implementation of idea to have bottom-bar to eliminate 'scrolling orgies'.



Only top voted, non community-wiki answers of a minimum length are eligible