Gotta love the attention to detail at the end, that is illegible when selected too. It's not realistic, though. Illegible sites never get that detail right.
They usually inhibit selection to protect their sacred text.
Death to Scroll Fade
151–160 of 232 posts
Re: Death to Scroll Fade
#152The HTML of that last paragraph sent me lmao
Re: Death to Scroll Fade
#153Something 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…
same thing intersects with ios safari when it hides top and bottom tool bars, hate that too.
and with the website doing the same thing, it's a mess.
Re: Death to Scroll Fade
#154Earlier quoted context omitted.
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
That’s not why user scrolls up, or at least not the only reason. For example, reading this discussion I constantly scroll up and down to center the text on screen.
If the header only appears after scrolling up for a bit then it’s not so bad, but most implementations show the header after scrolling 1px up. That’s infuriating.
Re: Death to Scroll Fade
#155> 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.
I want a reader mode that renders the page as if it were in an extremely tall window (ie. 10+ screens tall), then gives me a scrollable view of that static image of the rendered page. My browser should lie to the page on my behalf, and make it behave as if everything were already on-screen.
Materialistic[0] effectively does this (minus the screenshot part), not intentional I think (I belive it makes the webview as tall as the requested page and then uses the OS native scroll widget to add a scrollbar for it). The problem I regularly encounter with this is sites that have a vertically centered popup (cookie banner, newsletter, etc.), with a backdrop that obscures the whole page. You first have to scroll down quite a bit (half the size of the article) to be able to click the popup away.
Re: Death to Scroll Fade
#156Earlier quoted context omitted.
Anthropic uses it across all their websites, here's a typical example where the effect is obvious as you scroll down: https://claude.com/solutions/agents I could be wrong, but my simple guess is that it's become widespread in LLM-generated websites partly because of Anthropic's own style guides getting adopted through Claude-bundled skills and such.
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 not as bad because it's a much faster fade in, but I still find it incredibly obnoxious.
Re: Death to Scroll Fade
#157Something 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…
Oh god yes I absolutely hate those. Who on earth thought that was a good idea.
There is a special circle in hell where designers of such sites have to actually use the sites they design.
Re: Death to Scroll Fade
#158Something 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.
It's awful for the user. There is no reason why scrolling up should perform any other action then scrolling up the content. Zero benefit for anybody involved.
Re: Death to Scroll Fade
#159> 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.
what a good idea to have this automatically come up when the page opens, and perhaps give user a few seconds to press escape to get rid of it, if needed
Why just a few seconds? In reader mode you can press escape any time to close it.
Re: Death to Scroll Fade
#160Earlier quoted context omitted.
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
>It is vanishingly rare for users to scroll up when reading content unless they want to reach the top
This assumption is the problem. No, it is not rare for users to scroll up while reading. People are not perfect machines that read everything in one pass and understand it fully.
They may go back to re-read, or look at an earlier image or figure in the text, or otherwise. Sometimes people zone out for a minute and find they 'read' with their eyes but didn't actually take in the content. That requires going back.
For me, scrolling up to re-read is a basic use case of a web page. If it can't do that properly, it has failed.