Dustin L. Howett

Move AutoScroll down into Interactivity with a render timer (#20710) This pull request builds on the render timer infrastructure in #19330 and the pointer ID work in #20017 to move automatic scrolling down into the Interactivity layer. Leonard tells me that this is an acceptable use of the render timer infrastructure because it directly results in a new frame or new content being rendered (therefore, it does not spin the renderer for no reason.) Much of the code is the same. I recommend reviewing with: ``` git diff --color-moved=dimmed-zebra --color-moved-ws=ignore-all-space (git merge-base origin/main origin/dev/duhowett/wpf-1-autoscroll-to-interactivity) origin/dev/duhowett/wpf-1-autoscroll-to-interactivity ```

Localization Updates - 07/25/2026 03:03:40 (#20476) Co-authored-by: Console Service Bot <consvc@microsoft.com>

Add built-in glyphs for the first 149 "Symbols for Legacy Computing" (#20424) This PR adds the easy Symbols for Legacy Computing (U+1FB00...U+1FBFA) glyphs to our built-in glyph generator. The range covered includes sextants, eighth blocks of various sizes and counts, and new regtangular shades. They are likely to be used in ANSI-style art (probably by @PhMajerus, whose art this PR makes look even better.) -- I have not chosen to implement the other shapes _yet_. We need shaded triangles (probably another new shape, `ClosedFilled050Shape` or something.) But really, I stopped implementing at "checkerboard" because we would need either 8 instructions per glyph or a much larger checkerboard lattice implemented in the shader. Hand-coded, but I did write a web tool to aid me in assigning points (for all the trapezoidal ones) and a PowerShell script to generate bit patterns for the Sextants.

Guard and tidy a couple instances of GetActiveTerminalControl (#20458) This regressed with #19136. Closes #20457

drcs: reject attempts to write a glyph that is too tall (#20409) We probably shouldn't walk this iterator off the end of the array. Or write into it.

core, atlas: properly handle no-swapchain-handle situations (#20722) When ControlCore is set up to target an HWND, there will not be a swap chain handle. When there's not going to be a swap chain handle or a listener who cares about it, don't bother with the event registration (save memory on a useless object) and don't bother sending the event. Supersedes #20712

sui: fix the Spacebar on things inside settings cards (#20665) Okay, so, every SettingsCard inherits from ButtonBase. ButtonBase has its own local KeyDown/KeyUp handler, which can prevent the event from being bubbled at all. Moving our key handling to our local KeyDown/KeyUp handler allows us to decide when to involve ButtonBase's handler, rather than allowing it to delegate to us. Incidentally, this is probably why the implementer had to use the PreviewKeyXxx events; it was the only other way to get a "say" before the button handled it itself. Closes #20657 (superseded)

Core, Interactivity: allow our creator to provide a DispatcherQueue (#20713) This is in advance of the UWP/WPF unification work, where we need to provide a dispatcher from the WPF side. It should be a no-op today, but we could also move _loading_ the dispatcher up to TermControl (XAML).

Clamp the cursor position in bounds during "reposition with click" (#20442) This prevents us from crashing when we try to pass {-1, 3} into the Buffer. Don't know how we missed that. Closes #20443 Closes #19667

Disable Spectre mitigations (#50391) Spectre mitigations were briefly required for all MSVC-compiled code; however, it is no longer recommended best practice. These mitigations were always fragile and relied heavily on how the compiler generated the code. Removing mitigations here simplifies the build requirements.