Live data from Hacker News

The Scroll Up Bar

usabilitypost.com

81–90 of 118 posts

Re: The Scroll Up Bar

#81
The problem is that he's assuming the primary goal of the site's UI is to make reading the content as enjoyable and efficient an experience as possible.

Sadly, that's rarely the case.

A site like Forbes gets paid every time you click through to another article. Once you've landed on an article and you're reading it, your value to them has been expended. Thus they have almost a diametrically-opposed interest to yours- you want to read the content uninterrupted, and they want you to click another link.

Re: The Scroll Up Bar

#82

Someone has already mentioned my JS lib to handle this below, but as the author I feel compelled to mention it myself with some additional explanation. I built headroom.js [0] to handle exactly this. It simply adds classes at scroll up or down so you can be as fancy as you want (or not!) with the show hide effect. You can set a custom offset (eg. Don't invoke the hide/show mechanism until 100px down the page), you ca…

[deleted]

Re: The Scroll Up Bar

#83
Firefox Browser for Android's default settings requires you to scroll up somewhat rapidly on the page you're currently reading to reveal the browser's auto-hidden URL bar and menu. I tend to loathe this functionality because it means slightly losing my place every time I want to multitask when reading something.

I suppose it wouldn't be so bad as part of a website when viewed from a desktop environment, because you can easily highlight where you left off on the page much easier than you can on a tablet, for example.

Re: The Scroll Up Bar

#84
i agree with the post. but i just noticed on my desktop chrome browser that medium also applies the same behavior on here. i believe this is not necessary, as on a desktop i have plenty of reading space and this way im actually experiencing a less usable version of a website....

Re: The Scroll Up Bar

#85
After being into this field for quite a while now, I feel like there are no better web design than no web design.

Plain html works great on any device, is very readable, accessible and lightweight. There's nothing to lose in having 0 loc css.

Re: The Scroll Up Bar

#86

Fixed bars are annoying and should rarely be used. But what's even worse is when the mobile version helpfully removes the content or feature that you'd like to see. Please just have one site, make it efficient, and be done with it.

How do scroll up bars perform vs. bars that disappear / reappear on click (ie. http://demos.jquerymobile.com/1.4.0/toolbar-fixed/), anybody know?

http://ux.stackexchange.com/questions/57990/how-usable-are-b...

Re: The Scroll Up Bar

#88
post #13
post #5

I was hoping to read about a usability study done when I clicked the link. I do agree for blogs and articles but for web apps I'm not sold.

Right. Breadcrumbs and/or nav bars on apps are nice.

Indeed:

http://ux.stackexchange.com/questions/33071/are-breadcrumbs-...

Re: The Scroll Up Bar

#89

Fixed bars are annoying and should rarely be used. But what's even worse is when the mobile version helpfully removes the content or feature that you'd like to see. Please just have one site, make it efficient, and be done with it.

It's so much easier to fuck up mobile than it is to do it right. And if you're not doing it exactly right, don't do it at all. Here's what the EC2 console looks like on mobile: http://i.imgur.com/MfbCdhU.png It appears that Amazon is doing this on purpose... Yes... user-scalable=no

There was/is an iOS bug where changing orientation after zooming would cut-off some of the page, most websites simply disable all zooming to "fix" it. http://blog.pgrady.com/post/29511322784/fixing-the-ios-orien...

Re: The Scroll Up Bar

#90

Earlier quoted context omitted.

It's so much easier to fuck up mobile than it is to do it right. And if you're not doing it exactly right, don't do it at all. Here's what the EC2 console looks like on mobile: http://i.imgur.com/MfbCdhU.png It appears that Amazon is doing this on purpose... Yes... user-scalable=no

> Disabling user-scalable (namely, the ability to double tap to zoom) allows the browser to reduce the click delay. In touch-enable browsers, when the user expects the double tap to zoom, the browser generally waits 300ms before firing the click event, waiting to see if the user will double tap. Disabling user-scalable allows for the Chrome browser to fire the click event immediately, allowing for a better user exper…

[deleted]
Post reply on HN