Hacker News Reader

Comment by TheZenPsycho | Hacker News Reader

    In principle I agree with you. In this case apple's decision causes actual problems with content. Putting stuff in a scrollable iframe, or overflow scroll pane now involves carefully instructing people on how to scroll it. Or you force your own custom scrollbars. Or just not have scrollable panes-- you could argue that is a good thing, but sometimes they are unavoidable. Like, for instance, here on HN if someone happens to post an extremely long code segment.

if you are using a mac, remember that you need to scroll horizontally to read all of the above message.

on an ipad use two fingers to scroll it.

Do you get my point? Is the above a problem for HN or for Apple or for the User to puzzle out?

View on HN

In Safari, there's no visual indication that the content is horizontally scrollable. That's a problem.

In Firefox, there's a big scroll bar. This scroll bar consumes more visual space than the content it scrolls. That's an absurdity.

Scrollbars are a legacy UI element, a throwback to an era before scrolling mice and trackpads. You nicely illustrated a problem, but your proposed solution makes no sense on modern computers with dedicated scrolling gestures.

> Scrollbars are a legacy UI element, a throwback to an era before scrolling mice and trackpads

I think there's disagreement about that here, which in a manner of speaking, is behind the mixed opinions expressed in this thread.

I for one do not seek a browser without a scrollbar even though my mouse has a scroll-wheel. Making very large adjustments to my scroll position using the wheel is annoying: either I spin the wheel repetitively or I click the wheel and enter a scroll mode where the pointer's distance from a start point adjusts a velocity of scroll that continues until I click again. Both are much more fussy than just picking the scrollbar tack up and dragging it to the point I want to reach.

I don't even like that in IE 10 (Metro) the scrollbar disappears on my Surface Pro with its touch screen. Luckily for me, IE 10 (desktop) retains the scrollbar.

Good points. I should revise what I wrote to touch-enabled scrolling hardware.

With a scroll wheel, both fine and gross movements are more difficult. The scroll wheel has a fixed set of positions, and is optimized for scrolling a line or two at a time. I also have never liked the modal "scroll mode" that you describe.

With a magic mouse or scrolling trackpad, you get a much larger surface area available for scrolling, and there are more gradations. Inertia scrolling also makes it easy to scroll to the bottom or top of documents quickly: you can quickly "flick" to get to the bottom or top, which feels pretty natural.

As a result, I find I interact with the scroll bar a lot less on my MacBook Air than I do on my scroll-wheel equipped desktop. I'm not sure what the situation is like on Windows though.

> I'm not sure what the situation is like on Windows though.

Us poor Windows users have to hike few miles, find the cursor, lift and carry it on the back for a mile to get it to where we want it to, and then place it there. After all that, the page moves an inch.

I didn't propose a solution. I asked a question: Whose problem is it to solve? The user's? Apple's? HN's?

Apple certainly took it upon themselves to cause the problem. What's your proposed solution?

Scrollbars are hidden by default if OSX detects a Magic mouse/trackpad but there's nothing stopping anyone from changing that to always shown (or always hidden!), as well as the scroll direction.

Maybe the solution is a prompt for a decision the first time OSX starts up, at the same time as the user is creating their account?

add a prompt you say? do you think anyone actually reads prompts? or do they just dismiss them as quickly as possible, since they're in the way of the actual task?

I do get your point, and it's a good one. My opinion about allowing the user the luxury of having selected their preferred reading environment isn't so inflexible to say that you shouldn't afford users some concessions in a scenario such as this.

On my PC, I of course do see a scrollbar. In fact, I probably would not at first even realize that I need to instruct viewers on other platforms to interact with the content in any unusual manner. But once aware of it, given the capability to design my content differently to avoid the situation described, I would go with that. Failing that option, I would probably just put instructions in as you've done here.

I would fairly steadfastly refuse to implement my own scrollbar functionality because I'd likely fail to implement that in a manner all users on all devices would understand intuitively.

For the majority of scenarios, the browsers' default behavior will match the users' expectations and they will be able to consume the content I've created in the fashion with which they are accustomed.

As an aside, this conversation reminds me that legacy versions of IE (and maybe current versions; I've not checked) allowed one to affect the appearance of the browser's scrollbar through CSS.

I believe it to be neither and as a counterpoint ask if it really is a problem as you frame it. Scrolling on a touch enabled device, and all Apple devices are supplied touch enabled in one way or another, is performed differently. It is instinctive using OS X to scroll with 2 fingers. Obviously, this is a learned behaviour for adults that have been around computers for a while, but an intuitive one none the less. The old paradigm of scrollbar with arrows and thumb is redundant with touch input, to the point it actually gets in the way. What we have now in OS X and iOS serves more as a page location indicator that occupies the same position in the container.

Heh, funnily enough, it scrolls with one finger on the beta iOS. Although, I think they may have changed that in a previous safari update.

Minor correction: on an iPad, you can also scroll that text with one finger.

That is new. Apple has seen the light, finally.

Reply on news.ycombinator.com