Raymond Chen recounts Windows scrollbar shortcuts and where Shift+click still works

Raymond Chen, the Microsoft veteran behind The Old New Thing blog, has published a retrospective on Windows scrollbar shortcuts — including one he only discovered recently despite having been involved in Windows development for more than 30 years. The post, which surfaced on the Hacker News front page, doubles as a small case study in how platform conventions erode once every framework starts shipping its own custom controls.

Twenty years of five mouse targets

For the first two decades of Windows, Chen explains, the scrollbar control supported only a handful of operations. Taking a vertical scrollbar as the example, there were five things you could click: either arrow at the ends, which scrolls by a line; the two regions between the arrows and the thumb, which scroll by a page; and the thumb itself, which you drag to reach an arbitrary position. That was the whole vocabulary.

What Windows 7 changed

Windows 7 added a right-click context menu to the scrollbar. Chen lays out its seven options alongside their existing equivalents. Top and Bottom correspond to dragging the thumb to the start or end, or pressing Home and End on the keyboard. Page Up and Page Down match clicking the gutter regions or the PgUp and PgDn keys. Scroll Up and Scroll Down match clicking the arrows or pressing the up and down arrow keys.

The one genuinely new option was Scroll Here. Instead of grabbing the thumb and hauling it across a long document, you right-click at the point you want to reach and pick Scroll Here from the menu. Chen says he relied on this heavily for long jumps, because it lets you aim at your destination rather than manage where the thumb currently sits.

The same release also added a far less visible shortcut: holding Shift while clicking the scrollbar makes the thumb jump directly to the clicked spot. Chen admits he only learned this existed recently, having depended on his context-menu habit the entire time.

The fragmentation problem

The catch, as Chen notes, is that almost nobody uses Win32 scrollbars any more. Modern applications sit on frameworks that draw their own, and support for these conveniences is all over the map:

• Chromium-based apps, including Electron, omit the context menu but do implement Shift+click.
• The WPF XAML framework appears to implement both the menu and Shift+click.
• WinUI, Microsoft's newest XAML framework, offers neither — though Chen notes at least one person has requested it.
• Qt leaves the decision to each application, exposing opt-in style hints such as SH_ScrollBar_ContextMenu, plus separate hints for jumping to a position on left-click or middle-click.

Chen closes with a wry observation: by the time he finally learned about Shift+click, the ecosystem has fragmented to the point that he cannot count on the shortcut working at all.

Why it matters

The post is enjoyable software arcana, but it makes a broader point about consistency. Shortcuts like Shift+click are learned once and then trusted; when frameworks silently drop them, users get unpredictable behaviour rather than a uniform downgrade, which is arguably worse than never having the feature at all.

Discoverability is the other half of the story. Chen, an insider who has documented Windows quirks on The Old New Thing since 2003, missed a shipped feature entirely because nothing surfaced it. And with WinUI — Microsoft's own current framework — omitting both conveniences, the piece reads as a reminder that platform conventions do not survive on their own. Somebody has to carry them forward every time a basic control is reimplemented.