Windows Terminal v1.22.11751.0

[DHowett]

We have decided to hold off on promoting 1.23 to the Stable channel until our next release date in August. Until then--and you are welcome to speculate which direction causality flows--please enjoy these bug fixes!

Changes

• Icon and background image paths beginning with \\?\ will no longer trigger a validation error; fragment profiles will also no longer trigger any image validation errors; in addition, http sources for icons have been disabled to improve Terminal's security posture (Gently rework icon and background image validation #19044)
• On ARM64 devices, the default Visual Studio profiles will now launch using the ARM64 host tools on VS 17.4+ (Small enhancements for VS profile generation #19025) (thanks @reynoldskr!)
• Our DA1 report will now contain 52 to indicate support for OSC 52 (Manipulate Selection Data) writing to the clipboard when it is enabled (Indicate support for OSC 52 in the DA1 report #19034) (thanks @j4james!)

Bug Fixes

• IMEs such as Tencent's QQPinyin which request invalid color schemes will now reliably display their in-progress composition (Fix support for the Tencent QQPinyin IME #19046)
• Certain Win32 Console APIs and copy operations will now properly destroy Sixel images in the modified range (Fix two image erasure bugs #18855) (thanks @j4james!)
• SGR-encoded mouse reports for motion events now emit the final character M rather than m, which matches other terminal emulators (Fix SGR mouse movement reports #18864) (thanks @j4james!)
• Swapping panes should no longer result in both of them losing focus (Manually focus panes after swapping them #19024)
• Terminal will no longer experience uncontrolled re-entry into the atmosphere when it fails to save your settings (Display a warning if SUI is unable to write to settings file #19027)
• The Group Policy template archive is now automatically produced by the build system (release-engineering: package (during build) and upload GPO templates #18841)

Fixes backported from Preview 1.23

• The console will now more reliably wake up applications waiting for input during I/O contention (Fix a major stdin wakeup race condition #18816)
• When run with allowHeadless enabled, Terminal will no longer enter an unusable state when you close the last window ([1.22] Fix teardown when 'allowHeadless' is enabled #18869)
• ReadConsoleInput will no longer spuriously return success having read 0 characters (Properly implement WaitForData for ReadConsoleInput #18228)

Console Host Changes (future Windows version)

• Sixel images will now be scaled in a more visually-pleasing manner (Improve quality of GDI image scaling #18495) (thanks @j4james!)

NuGet Packages

• ConPTY: the NuGet package has transitioned away from the win10-* runtime identifiers, which is a .NET breaking change (thanks @mitchcapper!)
• The WPF control now defaults to using built-in box drawing and block element glyphs (wpf: force builtin glyphs #18906)
• The WPF control now supports receiving OSC 52 (Manipulate Selection Data) to write to the clipboard (wpf: allow OSC 52 to write the clipboard #18905)
• The WPF control now uses the new TSF implementation for braoder compatibility and better usability (wpf: use the new TSF implementation #18861)
• The WPF control package's embedded .NET assembly is now Strong Named (wpf: strong-name sign Microsoft.Terminal.Wpf #18836)

---

Binary files inside the unpackaged distribution archive bear the version number 1.22.250624001.

---

This discussion was created from the release Windows Terminal v1.22.11751.0.

[CCdaGr8]

I want to join

[CN-CODEGOD]

cool

[crramirez]

@DHowett

"Icon and background image paths beginning with \?\ will no longer trigger a validation error; fragment profiles will also no longer trigger any image validation errors; in addition, http sources for icons have been disabled to improve Terminal's security posture"

You should have released this "fix" first in preview, then on stable, and not straight to stable. Now many users will lose their distro icons, including Ubuntu installed from Store. It is particularly challenging now to include a fragment in the application that points to the right icon. Because you don't also support icon relative paths to the fragment.

We, application developers, now need to rush to figure out how to solve these issues.