Or, especially in news sites, Taboola and other bottom feeder trash.
"Sharedaddy" is another element to nuke (social link litter crap).
You see user-hostile shrinking of the scrollbar, someone else sees more room for content and hiding something that isn't necessary until you need it. You see loading content piecemeal as hostile, someone else sees blocking that 1kb of text from being displayed while you do more network-intensive work as hostile.
For additional aspects and details I refer you to these threads: https://hn.algolia.com/?dateRange=all&page=0&prefix=true&que...
I think that's a large contributing factor, but either most implementations are are as deficient [0] as what they are trying to augment or there are other things at play here. (Branding since websites haven't been able to consistently style browser scrollbars since the IE/early Firefox era; as the other comment points out, trying to counterbalance how long pages have gotten with "after-content" such as ads and comments and recommended articles and "infinite scroll" to more articles.)
[0] Or arguably worse deficient: Most of them seem to have no real accessibility themselves and are opaque to things like screen readers. Even if modern scroll bars are hidden by default and woefully tiny visually by default, they still have decades of accessibility baked in and accessible options (if you can find them).
I suspect a strong driver of scrollbar deprecation is the overwhelming dominance of small-screen touch-based mobile devices. An active scrollbar, that is, one which not only shows page scroll depth, but controls it via touch, is one more UI element to generate annoying behaviours given the already perilous state of touch-based UIs. (The inability to correctly distinguish tap vs. drag or scroll actions is one that's driven me to distraction for well over a decade.)
Unfortunately, what's at least arguable on mobile becomes the trendy fashion on desktop, which is just fucking stupid.
It's possible to essentially reimplement the logic of how scrollbars look, where they are, and when they appear, in just CSS on modern browsers.
Ended up having to do part of that once because it was easier at the time than to figure out just why a mismatched browser scrollbar would show up due to complex layouting issue (in embedded world, so we didn't actually have to worry about end user preference there, otherwise I wouldn't dare use such a hack)
Especially since in our case I essentially deleted the scrollbar.
There are browser configuration tweaks which can be done in at least some cases. On Firefox Mobile / Fennec, for example, there's a configuration hack which can be done.
I'm having trouble tracking that down but I think this might be it:
In about:config:
### scrollbar width
widget.non-native-theme.scrollbar.size.override 30
### scrollbar shape
widget.non-native-theme.scrollbar.style 4
From: <https://old.reddit.com/r/firefox/comments/ujo1xy/how_to_incr...>I'm #notafan of customising site scrollbars. But I've written my own CSS to do that (used only on my own, non-public, Web pages), and man is it a breath of fucking fresh air.
There are other apps which are similarly fucked in this regard. Mozilla's Pocket comes to mind.
Yes, I use a big screen, but borderless and clean windows allows me to fit more content into the screen and is less distracting in general.
Moreover, almost all mice I used except the most basic ones have horizontal scrolling capability.
So we should be able to easily choose whatever default we want.
At this point, I would pay good money for an actual user agent that is worthy of the name.
I wrote a rant about this on my blog last month. https://blog.melnib.one/2024/05/19/death-of-the-user-agent/
Scrollbars do two things. They let you scroll (duh), but they are also progress indicators. There are other ways of scrolling (e.g. swiping on mobile) which work by default. But there is no other default way of showing progress. I don't particularly like the progress bar example in the original post, something as unobtrusive as a percentage in the bottom right corner would work just as well. But I do want some indication of progress ...
That is, a classic desktop scrollbar, dating back to Xaw widgets, the original Apple desktop, and even earlier[1] not only shows where you are within a text or display, but allows you to control where you are typically by clicking on elements of that scrollbar: the cursor, the bar itself, and the endpoint arrows. Several of these had interesting / quirky / annoying variants on interaction (those familiar with early X11 Xaw widgets can likely think of several).
There's an interesting static image comparison at Reddit:
<https://www.reddit.com/media?url=https%3A%2F%2Fi.redd.it%2Fe...>
And a much more informative interactive demonstration by Sébastien Matos from 2019:
<https://scrollbars.matoseb.com/>
Discussed on HN a year ago: <https://news.ycombinator.com/item?id=36307341>
And subject of quite a good review by The Verge: <https://www.theverge.com/2019/11/1/20943552/scroll-bar-visua...>
Another point on swiping: my mobile device for the past three years has been an e-ink tablet. And I've learnt that swiping absolutely sucks. E-ink displays are much faster than people seem to believe, but there's still lag that an emissive display lacks, and it's far better to page through a long text or display than to scroll through it. I've all but entirely adopted an e-ink optimised browser that mostly does this, EinkBro (based on FOSS Browser), and I am constantly trying to page through other apps by tapping where EinkBro's forward/back touch zones are. People who've used other ebook readers will be familiar with the general concept as most have similar features. Having to imprecisely scroll through a document or app is exceedingly painful.
Scrollbars partially solve this problem as for most, tapping above or below the cursor will advance the display by about a page of text (some feature a few percent overlap). On desktop systems, there's an even better option: the space bar. For a whole slew of apps and tools, dating back to Unix's pg, more, less, most, etc., you can page through a long text one screen at a time by tapping the space bar, which is the largest damned key (and hence the easiest-to-hit target) on the keyboard (Fitts's Law[2]).
By contrast, scrolling on mobile:
- Is highly subject to the tap-vs-drag confusion: the GUI cannot consistently distinguish a tap action (interacting with the application) with a drag (changing the viewpoint).
- Is imprecise both by contact point (that is where you're interacting with the display) and displacement amount (how far you're moving through a text or app). You might scroll by more or less than a page, and it takes considerable time for the eye to recapture the reading point.
- Obscures what it is you're interacting with. Your finger is covering the display you're trying to manipulate. A desktop mouse cursor by contrast covers little or none of the text or app.
- Is subject to further confusion based on dynamic characteristics of the document or app you're dealing with (e.g., a Web page with progressively-loaded or rendered elements, or on Mozilla Pocket, inconsistent placement and textblock wrapping around image elements).
I come to desperately hate scroll-based interfaces these days.
________________________________
Notes:
1. I wanted to claim provenance to the Mother of All Demos in ninteen-and-motherfucking-sixty-eight, but can't definitively show that Englebart included scrollbars. Wikipedia does give a 1974 implementation in Bravo: <https://en.wikipedia.org/wiki/Scrollbar#History_and_progress...>, citing <http://bitsavers.trailing-edge.com/pdf/xerox/alto/Alto_Users...> (PDF).
2. Which dates to 1954!!! <https://en.wikipedia.org/wiki/Fitts%27s_law> See also <https://doi.org/10.1037%2Fh0045689> (Fitts, 1964) and an extensive bibliography: <https://www.yorku.ca/mack/RN-Fitts_bib.htm>.
And the icing on the cake - as demonstrated in the quanta link - is the horizontal rendering in combination with a generous sticky wasting precious space I'd rather use for, well reading content.
This is addressed though in the following paragraph (indirectly), where a table of contents is rendered on the side. (Similar is a minimap, which I like for code or complex articles, but not for long text-heavy articles.) Maybe you also hate that, but it actually serves a purpose that scrollbar can never replicate and is much more useful than a scrollbar for many people.
> One immediate thought is that this is completely superseded by the regular browser scroll bar that’s ever-present at the side of the page. However, the scroll bar could be deceiving. If your page has a comments section, the comments could make the page look dauntingly long. Similarly, references to other pages and general “footer material” count towards the scroll bar, but would not count towards the progress bar.
> Combining the two, you could imagine an always-visible table of contents that highlights the current section you’re in. With such a feature, you can always see where you are (including a rough estimate of how far into the page you’ve scrolled), and at the same time see how the current section integrates into the broader structure.
The same thing happens with books that include references at the end — a print book can be 20% endnotes. I've even encountered bizarre EPUB's where for some incomprehensible reason there's a page break between each endnote, so the actual content of the book ends somewhere around the 5% mark of total page count.
I actually really appreciate a super-thin (2px) progress bar in the header.
I don't like an always-visible table of contents because I find it really distracting. But I really like the way Wikipedia does it in their app, where it's a single tap to reveal the table of contents full-screen, centered on and highlighting your current section.
I'm just really glad that we seem to have mostly moved past headers that expand down in front of the content you're trying to read as you scroll down the screen. I can't think of a single justifiable reason for this behavior, but it was all the rage for a while. Also, I suspect the progress bars resurged because browsers became enamored with invisible or barely-visible scroll bars.
I really hate progress bars, they are incredibly distracting. One of the worst examples of front end programmers wasting their time reimplementing browser functions badly. I already have scroll bars! I do not need more scroll bars!
Also, link decoration: my browser already has a nice discreet indicator to tell me where a link goes, I don’t need or want mysterious dingbats in the running text. (It reminds me of websites that are so scared of hyperlinks that they send them via interstitial warning pages “YOU ARE LEAVING THE SITE!!!!1!1!”, or in a recent case via a $yber$ecurity box that broke the link completely.) And preview popups? Get in the sea, hostile obnoxious interruption.