For as long as I can remember, I’ve been having issues with scrolling in Windows and its applications. When scrolling via dragging the scroll blob, it seemed as if Windows had the annoying habit of randomly resetting your scroll blob to its starting position, which irritated me to no end. It took me a while to figure out, but I finally know when this behaviour occurs – now I just need to know: why?!
In case you’re unfamiliar with my personal graphical user interface lingo, the scroll blob is that little thing inside your scrollbar which indicates where in a document you are. It can also be used to scroll through documents, by clicking and dragging it up and down (or left and right for horizontal scrollbars).
Before we dive into the problem I mentioned, there’s actually quite a few interesting things to say about scrollbars and the scroll blob. As most of you will know, the scroll blob is proportional; the smaller it is, the larger the document you’re viewing, and vice versa. For me personally, the blob’s most memorable role is that it serves as a sort of taunting reminder of just how much more illegible scientific drab I have to wade through during studying.
Then there’s the issue of scrollbar behaviour. Clicking inside the scrollbar, but outside of the blob, can have two different outcomes, depending on system settings and operating system used: the right one, and the wrong one. Because the scroll blob is proportional, you would expect the scrollbar to be proportional too; as such, the only correct behaviour when clicking inside the scrollbar is “jump to here”. The incorrect, inconsistent, annoying and obnoxious outcome is “move one set arbitrary distance down/up”. The former outcome indicates that the computer thinks I’m smart, while the latter indicates that the computer gives me a reassuring pat on the back, thinking “I know what’s best for you, now shut up”.
Yes, any system that uses the latter setting is wrong. Non-negotiable. I’m quite strict on this. Oh, and I base it on absolutely no evidence whatsoever.
Finally, the issue of the scrollbar arrows. There is only one correct way of displaying the scrollbar arrows: grouped. BeOS already knew this, and who are we to argue with what is probably the best operating system of all time? In all seriousness, the reason grouping them is better is that it reduces the amount of mouse movements you need to make when scrolling. Sure, mouse wheels and the like have reduced the significance of the arrows considerably, but I still sometimes find myself using them. On top of that, I dislike touchpad scrolling, so on laptops I’m pretty much confined to the arrow keys and the actual scrollbar itself.
Now, moving on to the actual problem at hand. The problem I see is that during scroll blob drag operations, Windows creates an invisible “hotspot” around the scrollbar; if you move your mouse cursor outside of this hotspot while still dragging the blob, it will reset itself to its initial position. If you’re still holding down the mouse button, the reset is visual only; moving your mouse pointer back into the hotspot will “undo” the reset. If you release, however, the reset will become permanent.
The actual problem here is that this hotspot is too small. The below screenshot indicates the size of the hotspot.
The width of the hotspot is sort-of adequate; you’ll rarely find yourself veering off that far east or west (but it does happen). The real issue here is north and south: as you can see in the shot, there is barely any space to move your mouse before the blob will reset itself. I use the blob drag behaviour all the time (especially on sites with lots of comments, like OSNews), so I run into this annoying problem continuously.
The million dollar question here is why on earth does this hotspot exist in the first place? Can anyone think of any scenario in which this behaviour is even remotely useful? I did a little digging around, and found that even in 1999, people were complaining that KDE had adopted this annoying scrolling behaviour. Karl Fogel already concluded back then that Microsoft actually had to write additional code to get this behaviour.
The solution to this bug is drop-dead obvious: ditch the hotspot. It serves no purpose, other than to annoy and aggravate people. I should be able to move my pointer to hell and back while dragging the blob without it resetting the scrolling position.
Can anyone tell me if other systems have been affected by this bug as well? Does KDE still have it? GNOME? Mac OS X?