Live data from Hacker News

Who Killed the Scrollbar?

ello.co

171–180 of 325 posts

Re: Who Killed the Scrollbar?

#172
"Lord knows, you can't actually grab the scrollbar and navigate with the bloody thing."

Do these people not have scroll wheels or scrolling gestures on their touch devices? I get it that some content is too long for scroll wheels, but it's just bad design if you are having to contend with data sets that are that large.

This just screams of old people screaming about change that they are not comfortable with... and I'm old AF.

Re: Who Killed the Scrollbar?

#173

If you want to have a good scrolling experience with quick navigation for long articles on mobile try Opera browser. Opera double tap zoom is also the only one that can relayout non-mobile friendly desktop paragraphs to mobile format.

Thanks for the recommendation, though really this should be consistent for an entire OS or at least application framework (native and web), not something that varies app-by-app.

Though if Opera are getting this right, good on them.

Re: Who Killed the Scrollbar?

#174
post #123

Earlier quoted context omitted.

I don't really understand what's wrong with a full-screen modal menu, or how that means "this is for mobile." It's true that it looks a bit stark on their homepage where there are only 2 links, but it's probably a fairly sensible extensible design that works well when there are many more links or things to see. It's fair to criticize specific visual and UX design details, but it's a bit much to take this as any indic…

Because I'm trying to read off some details on a document I have open on the side while interacting with the menu and then it goes full screen and obscures everything.

Fair enough. I only see two links in the menu, so surely the menu can quickly be viewed and closed.

Re: Who Killed the Scrollbar?

#175
post #65

Earlier quoted context omitted.

Oh you're right. Interesting. My browser is 1134x1080. I guess maybe in today's world of super high res phones that could be considered a "mobile display".

I don't think it has anything to do with resolution. I'm getting the same thing as the parent on my 1366x768. Edit: It's actually the width that matters. After reducing it a bit it will show the hamburger menu.

The media query for the hamburger button is max-width: 1366px, so you just met the cut off. I couldn't find a media query for the menu itself, but I suspect since the hamburger button is what allows it to get created, they didn't feel the need.

Re: Who Killed the Scrollbar?

#176
post #163
post #39

Earlier quoted context omitted.

I can see why they did it. Now that screens are ~universally 16:9, vertical space is at a premium. It would be nice if the hamburger menu actually replicated the same functionality though.

16:9 is a ratio whereas the amount of vertical space is an absolute amount. I don't think the two are related, unless screens got wider at the expense of height, which surely is not the case.

They did lose height; 1600×1200 → 1920×1080. For a while you could find 1920×1200 if you looked hard and spent more, but at the next increment everything is 16:9.

Re: Who Killed the Scrollbar?

#177
post #51

Earlier quoted context omitted.

I see this happening a lot. "Mobile first!" doesn't mean "Mobile only!"

I've had to conclude that they think (or hope) that everybody not using a phone is using a tablet.

Yeah, but surely the vast vast majority of dropbox's business has to come from PCs. Given how hard (and wrongly) they are pushing to be a collaborative space for work documents, I think I must be correct about this. I know it's cool and all to imagine everyone working on their phones, I just can't see that as a viable work process atm.

Re: Who Killed the Scrollbar?

#178
post #88

Earlier quoted context omitted.

> I prefer it to disappear when I don't need it. My strong preference is the exact opposite of this. I want it to be there, full size, any time that scrolling is possible. It seems that this is something that should be user configurable.

System Preferences > General > Show scroll bars: Always

OMG you just brought an enormous amount of happiness to my life! these disappearing scroll bars were a nemesis of mine and i have been blaming Chrome for this calamity. thank you so much :)

Re: Who Killed the Scrollbar?

#179

Earlier quoted context omitted.

I often do. I've been (occasionally) experimenting with slight bowderilisation. For better or worse, less swearing tends to go over slightly better. I can assure you the feeling was there in the original. My general administrative announcement (NSFW langauge): https://ello.co/dredmorbius/post/dlz9c2z6x-tvkd7rxtxwpw https://mastodon.cloud/@dredmorbius/100521241625879766

Thing is I felt distracted by the amount of swearing, and the fake swears just exaggerated that. I don't care about the swearing in principle, it just felt misplaced in your article, in particular in this censored form. Swearing helps convey frustration etc. and I guess that's what you were going for, but it doesn't actually work for me (as the reader) in all cases and in particular when it's "redacted". Not that my…

Fair points.

I wrote that some three years ago, among a series of rants (I don't recall the others that accompanied it), moved to extreme annoyance, and after looking at the initial result, decided to replace the initial language to tone it down a bit.

Today I tossed it into the HN submissions queue following an earlier item on similarly obnoxious and undiscoverable UI/UX, and was surprised to see the item take off. Planning which HN submissions will succeed is not a high-probability endeavour.

The best way to read the language is "yeah, the author was pretty annoyed when they wrote this, but decided to tone down the effect without removing all references to that annoyance entirely".

I've written highly invecitve-filled pieces elsewhere. For public or private consumption. It's when I stop any swearing that feedback (and usage) is quite likely to stop -- the outrage is a measure that I still care. Users past caring don't remain long.

Post reply on HN