Live data from Hacker News

Death to Scroll Fade

dbushell.com

141–150 of 232 posts

Re: Death to Scroll Fade

#141

Earlier quoted context omitted.

Who thinks like this? The last thing I want on a website is surprise. I want to do what I came there to do, the same way it worked last time, and then get on with my day.

On a Web site or anywhere else. Apple, Microsoft, "flat design," and peek-a-boo UI all insult the user and waste his time by turning an important tool into an Advent calendar.

s/micro intentions/micro aggressions/

Re: Death to Scroll Fade

#142

Something else scroll-related I personally hate: Sticky 'headers' that disappear when you scroll down, and appear when you scroll up. I hate them so much. It hurts my brain to see the stupid thing appear and disappear constantly if I scroll around a page. The worst part is you can't even zap them out of the way with something like uBlock, because then there's no header even when you're at the top of the page. >:( EDI…

[deleted]

Re: Death to Scroll Fade

#143

Earlier quoted context omitted.

Browsers have handed way too much control to web developers. "The web as a software SDK" was a terrible idea.

The web should be a method of delivering documents exclusively, and be limited to the kinds of things you can do with other computerized documents (the basics, but also Audio, Video, Animations, hyperlinking, etc.)

I'd be okay with locking these heavily-abused features behind a "web app mode" that the user has to enable on a per-site basis. It should include a restriction forcing all content to come from the same origin, so that the browser in that mode won't make it easy for web apps to include third-party tracking or advertising.

Re: Death to Scroll Fade

#144

Something else scroll-related I personally hate: Sticky 'headers' that disappear when you scroll down, and appear when you scroll up. I hate them so much. It hurts my brain to see the stupid thing appear and disappear constantly if I scroll around a page. The worst part is you can't even zap them out of the way with something like uBlock, because then there's no header even when you're at the top of the page. >:( EDI…

This only really works easily on desktop and requires a click, but is very satisfying to use:

https://alisdair.mcdiarmid.org/kill-sticky-headers/

Re: Death to Scroll Fade

#145

> This post purposefully ignores the reduced motion preference to give everyone the same truly terrible experience. I am sorry. Please use your browser’s reader mode. "Reader Mode" shouldn't even be a special mode. It should just be the default browsing experience, and users who want all this styling crap should have to enable "Clown Mode" or something.

"should have to enable "Clown Mode" or something." Bwahahaha, +1! This reminds me of calling Windows XP's default motif "Fisher-Price" mode. Which, sadly, looks professional and efficient compared to Windows (and, increasingly, the Mac) today.

I like that Apple was trying somwthing that has a little more texture and soul to it, but Liquid glass needs a lot of work to be made more subtle and usable. 10 out of 10 idea, 3 out of 10 execution.

Re: Death to Scroll Fade

#146

Earlier quoted context omitted.

This is literally the best ux pattern you can have. It is intuitive - user immediately discovers it when performing the obvious action, it increases the user experience (more text to read) without any real downside. It is the first thing I suggest to anyone when I see someone didn't implement it. I've never heard a complaint about it until now.

The user discovers it because it is practically forced on them. It is awful UI.

When a user wants to return to the navigation bar at the top he scrolls up. The navigation bar then immediately gets nearer.

The user discovery happens because the act he performs provides the exact intent you need to give him the shortcut.

Also for clarity this is only relevant for content based sites and not apps. It is vanishingly rare for users to scroll up when reading content unless they want to reach the top

Re: Death to Scroll Fade

#147

Earlier quoted context omitted.

I don't understand why browsers ever let designers fuck up the scrolling mechanism in the first place. Why is that even possible?

Browsers have handed way too much control to web developers. "The web as a software SDK" was a terrible idea.

My biggest annoyance: letting scripts control the history. I can imagine that someone thought "oh it'll be nice, you can use it for pages of an app". But the reality is that people are not nice and it gets used maliciously all the damn time. It should not be allowed.

Re: Death to Scroll Fade

#148
post #87

Earlier quoted context omitted.

That's a bit different since those are separate chunks of content rather than running prose (and they're mainly meaningless marketing fluff anyway). I don't find it all that annoying compared to the original article.

It's still incredibly insulting to waste the user's time trying to force them to read the page sequentially instead of being able to immediately scroll to the chunk of content they are actually trying to find. Especially if it is not the user's first visit to the page.

Studies show that viewer comprehension is strictly worse for presentations that use “build” animations vs ones that do not.

I assume the study results would be the same if they were repeated using fade scrolls.

Re: Death to Scroll Fade

#149

Why do web animations get so much hate with the HN crowd? I think a website is similar to a painting. Some will make you dizzy by just looking at them, and others will be a minimalist dream. Don’t hate me HN, but I say keep messing with the scroll bar, keep making annoying blinking banners, have your way with scroll fade. Don’t listen to these web dev veterans, they are just like snobby movie critics!

They get hate because they are almost always annoying and distract from the actual content. Nobody cares how creative your web page design is if it sucks to use so badly that a plain text page would be better.

Re: Death to Scroll Fade

#150

Something else scroll-related I personally hate: Sticky 'headers' that disappear when you scroll down, and appear when you scroll up. I hate them so much. It hurts my brain to see the stupid thing appear and disappear constantly if I scroll around a page. The worst part is you can't even zap them out of the way with something like uBlock, because then there's no header even when you're at the top of the page. >:( EDI…

This is literally the best ux pattern you can have. It is intuitive - user immediately discovers it when performing the obvious action, it increases the user experience (more text to read) without any real downside. It is the first thing I suggest to anyone when I see someone didn't implement it. I've never heard a complaint about it until now.

This is only true if you assume users always scroll down while reading and the only reason they scroll up is to find the header... but many of us scroll up and down while reading and find the re-appearance of the header to interfere with our goal of reading the content. So there is a clear downside for us "up and down" readers.

I don't know what portion of users we are though, I'm glad to see I'm not the only one!

Post reply on HN