Urgent.News

What's breaking now, across thousands of outlets.

Tech

A brief history of Windows scroll bar shortcuts

The scroll bar control in Windows has had a relatively simple set of operations over the past two decades. These include scrolling by line using the arrows at the ends, scrolling by page using the region between the thumb and arrows, and dragging the thumb itself to a specific position. In 2007, Windows 7 introduced a right-click menu on the scroll bar, adding options that mirrored existing mouse and keyboard actions, as well as a new feature called "Scroll Here".

This context menu allows users to right-click directly on a desired scrolling location and select "Scroll Here" without having to grab and drag the scroll bar thumb. This shortcut proves especially useful for navigating long distances without worrying about the starting point.

Parallel to the introduction of the "Scroll Here" feature, another hidden shortcut emerged. Holding the Shift key while clicking on the scroll bar would immediately position the thumb at the clicked location. This shortcut was not widely known, as users often relied on the more familiar context menu. However, with the rise of frameworks like Electron, Chromium, WPF XAML, and WinUI XAML that use custom scroll bars, the availability and functionality of these shortcuts vary.

While some frameworks adopt the context menu and Shift+click shortcut, others like WinUI do not. Raymond, an expert in the field, has been documenting the evolution of Windows for over 30 years. He began The Old New Thing website in 2003, which has since grown in popularity and now includes a corresponding book. Occasionally, Raymond contributes to the Windows Dev Docs Twitter account, sharing his insights into the history and development of Windows.

Written by urgent.news from Hacker News's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

This story

This is one outlet's version. Read the fullest account.

Read the original at devblogs.microsoft.com →

More in Tech

Three rules read the declared level. None of them read its other copy.

Our submission template asks a package to declare one thing: its contribution level -- case study , system , or theory+empirics . Three separate rules read that field.

  • Three rules govern declared contribution level
  • Rules check registration, manuscript, README.md
  • No rule compares copies for consistency

When every check blocks, verifying a small change costs an hour

Your pipeline started out fast. Then someone added the end-to-end tests, because they caught a real bug. Then the security review, because it caught another one.

  • Pipeline checks increased from swift to nearly an hour per small change
  • Model-assisted interface review was most time-consuming check
  • Tiered check system reduced per-task gate time to minutes

More from Wednesday 23 September →