5 ms·
Umm, scrollbars nowadays are just to indicate something is scrollable. You almost never have to actually drag them. Touch devices: swipe the content. Laptops:
by cabirum 3y ago
Umm, scrollbars nowadays are just to indicate something is scrollable. You almost never have to actually drag them.
Touch devices: swipe the content.
Laptops: touchpad two-finger swipe, hold middle button and use trackpoint
Desktops: mouse scroll wheel, pg-up/dn
What am I missing?
- oneeyedpigeon 3y ago> Umm, scrollbars nowadays are just to indicate something is scrollable. Which makes the often-default behaviour to autohide them all the more ridiculous! > Touch devices: swipe the content. Agreed; scrolling is one of the things that touch input just beats everything else at hands down. > Laptops... Desktops... Those still lack the 'click to move instantly to given point in document' functionality, right?
- cabirum 3y agoScrollbars were never meant to jump instantly anywhere. They are intended for progressive movement in either direction. It's a much more recent feature implemented as "minimap" in several IDEs. The difference is that minimap actually renders preview of the content to jump to, so you don't jump blind. Add: autohide is there because oftentimes it is obvious content can be scrolled by observing it does not fit entirely in the viewbox.
- oneeyedpigeon 3y agoIt's quite possible to have the best of both worlds, with arrow icons for progressive movement and clicking the bar to jump instantly.
- NekkoDroid 3y agonot just that, but for example my mousewheels sensor is basically unusable (when I scroll either direction its just roulette if it wants to scroll up or down or a mix of both) so I often use the middle mouse click to scroll... ends up not a lot of applications other than browser based ones support this.