I Want My Scrollbar Back
aartaka.me
aartaka.me
How did we get here? It seems in the late 90s/early 00s, we did tons of usability studies and formed our UIs and UXes around the results. We wanted to appeal to everyone.
And now, we've thrown it all away. Functionality is hidden. Discoverability is considered ugly and cluttered. Usability is thrown out the window in favor of something that looks "sleek" or "clean".
I've personally decided that rejecting a design purely because it's "dated" and not on any technical merits is evidence that you don't know how to think for yourself and just follow trends, whether they're good or bad.
It would show scrollbars, enumerate every shortcut, hilight everything clickable, indicate everything draggable, indicate everything right-clickable, etc.
Then perhaps an OS-setting to keep it permanently active.
Both Mac and especially newer windows has a huge number of weird hidden shortcut options that I still haven't learned after 5-10 years.
Same with phones, weird things like holding the spacebar on the IOS keyboard to scroll through your prior typed text.
I would guess it's an unholy confluence of putting people who prioritize appearance over usability in charge of UI design, plus the diminishing actual returns of computer technology coupled with an incessant pressure to "innovate."
People aren't rational, and the meme "new is improved" helps paper over a lot of dysfunction.
I think it is lazyness. By that I mean these toolkits are so complex, things get dropped because it would probably double development trying to get 5% extra into the product.
They might be at an API level. At GUI level, they are very simple.
Every so often I use some old windows native gui apps and lament how clear the ui is and how fast they run
It's discouraging to think about how much time gets wasted on useless or even regressive work. Once I started seeing this everywhere my tolerance for pointless refactors and redesigns went to zero.
That's not to say that changes are always bad, but the burden of proof should be on the side arguing to toss something that works for $ShinyNewThing, but in the tech industry the bias is usually on the opposite side. Newness gets lauded for the sake of being new and objections get stifled by the trend followers saying that you are afraid of change or don't appreciate evolution. No, I've just seen the same hype cycle play out enough times that I'm sick of wasting my time on bullshit.
From what I heard, this was the reason Apple only shipped their mouse with a single button for so long. They didn't want developers to hide things away in right-click menus; everything should be somewhere else and discoverable by looking at the UI. Shipping with a single button mouse, even when they supported right-click, was a way to force developers not to get lazy with it, since they couldn't count on users having a right-click on their mouse (or knowing control+click was a thing).
Designers and PMs don't get promoted for keeping things the same. So they went ahead and broke usability and gave each other high fives for making the UI "modern".
There are many variations of this theme. Look at Google Maps. It was solved a decade ago. Whoever built it has presumably moved on. New people are in charge and they won't get promoted if they leave it untouched. With every change, usability gets worse.
It was good when you could instantly stop all incoming data from a website with a single click.
And you had a status bar at the bottom of your browser that displayed the source address of each piece of data as it was coming in.
You could always refresh later if you thought you were missing something.
So much garbage is now unstoppable.
for a while i feel like chrome developer console had the ability to pause (and step thru) js.
i don't see that button anymore... am i crazy? did that ever exist?
"The debugger statement invokes any available debugging functionality, such as setting a breakpoint. If no debugging functionality is available, this statement has no effect."
If you load the page normally without inspecting it, these debugger statements are ignored.
You could attempt to read google documentation and spend hours not learning how to do something.
Everyone got on the bandwagon for dynamic web pages, parallel rendering, and such, which is fine. What isn't fine is when, due to said parallelism, the interface hops, skips, and jumps all over the damn place.
It's becoming clear that half the reason folks do it is because there's a slow to load ad they render right next to that critical action button/link and....Oops! Guess you wanted to find out that one trick X hates when you do it (but can't stop you) instead. Ad revenue goes up.
The Firefox solution worked for me.
I forgot to mention that there was a 900+ comment HN thread on scrollbars at https://news.ycombinator.com/item?id=37864867 which is where I found that link.
The web browser is supposed to be the User's Agent, not the web developer's agent. Web pages' look and feel should reflect how I have configured my browser, now how some UX designer 3,000 miles away from me dictated. If I want scroll bars, web sites should not simply decide to hide them. If I want 36pt pink text in Comic Sans, web sites should not simply decide to ignore that and use 6pt gray-on-white Helvetica. If I want to use my entire monitor, web sites should not simply decide to put 6 inch wide whitespace borders on each side so I have to scroll through a narrow strip of text to read the page.
I'm browsing more and more pages using my browser's "No Styles" setting, although many sites seem to go out of their way to make the "No Styles" experience horrible. Some browsers have "Reader Mode" too, which often works and honestly should be the default.
It's really frustrating when I want to just skim a page quickly and my options are you use my scroll wheel, or fight to click right on the thin a* scroll bar..
I know every shortcut to scroll possible. Nothing comes close to navigating long documents than a meaty scrollbar. With current display aspect ratios, I can afford to lop 40 pixels off my screen for this one affordance.
?
- You can have the UI/UX affordances that you prefer, but you resent the fact that they’re not the default affordances (and so have to affirmatively set them to match your preferences)?
- You can have the UI/UX affordances that you prefer, but you resent the fact that other people have other preferences (and wish your preferred defaults to be the only options for those affordances)?
- Something else that’s less clearly inferred?
"Scrollbars are becoming a problem" https://news.ycombinator.com/item?id=37864867
--> https://artemis.sh/2023/10/12/scrollbars.html
which offers several solutions.
Browsers have (stateful) per-site zooming and if you want all text everywhere to be bigger, operating systems (including mobile) let you adjust this at the system level.
Makes my large high dpi monitors almost pointless.
If you want to jam in more ads, the real shithead trick is to split the story/article across multiple pages, so you get multiple page-loads per story.
For a significant number of people, they don't get any benefit from a widescreen display, because all that extra space is just empty screen due to max-width being set on the text. Of course, if the developer didn't do that, the text would be hard to read. They're saving users from themselves in many cases.
I have a site where I don't use any CSS and have a note to tell people to make their browser more narrow if they need the text to wrap so it's easier to read. Doing that, the site works on everything, no media queries required.
Even if not interacting with it, the scroll bar is a visual aide telling the size of the page and the location within it.
I bet you never used a mouse wheel on Windows 10. /s
(Some time ago MS decided that focus follow mouse shall not be used anymore for mouse scrolling)