Release SDK 1.0.2420.47, for Runtime 123 (Mar. 25, 2024)

Release notes for Microsoft Edge WebView2 SDK, release date: Mar. 25, 2024.

NuGet package for WebView2 SDK 1.0.2420.47

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime 123.0.2420.47 (Mar. 25, 2024) or later.

Detailed contents:

• Promotions to Phase 3 (Stable in Release)
  • Hit-testing results on regions
  • FailureSourceModulePath property
• Bug fixes
• See also

Promotions to Phase 3 (Stable in Release)

The following APIs have been promoted from Phase 2: Stable in Prerelease, to Phase 3: Stable in Release, and are now included in this Release SDK.

Hit-testing results on regions

Added a new API to provide hit-testing results on the regions that a WebView2 contains. This API is useful for visually hosted applications that want to handle mouse events on the non-client area of the WebView2 window.

Previous phase: Hit-testing results on regions in Prerelease SDK 1.0.2415-prerelease, for Runtime 123 (Feb. 26, 2024).

.NET/C#

• CoreWebView2CompositionController Class:

  • CoreWebView2CompositionController.GetNonClientRegionAtPoint Method
  • CoreWebView2CompositionController.NonClientRegionChanged Event
  • CoreWebView2CompositionController.QueryNonClientRegion Method

• CoreWebView2NonClientRegionChangedEventArgs Class:

  • CoreWebView2NonClientRegionChangedEventArgs.RegionKind Property

• CoreWebView2NonClientRegionKind Enum

  • Caption
  • Client
  • Nowhere

• CoreWebView2Settings Class:

  • CoreWebView2Settings.IsNonClientRegionSupportEnabled Property

WinRT/C#

• CoreWebView2CompositionController Class:

  • CoreWebView2CompositionController.GetNonClientRegionAtPoint Method
  • CoreWebView2CompositionController.NonClientRegionChanged Event
  • CoreWebView2CompositionController.QueryNonClientRegion Method

• CoreWebView2NonClientRegionChangedEventArgs Class:

  • CoreWebView2NonClientRegionChangedEventArgs.RegionKind Property

• CoreWebView2NonClientRegionKind Enum

  • Caption
  • Client
  • Nowhere

• CoreWebView2Settings Class:

  • CoreWebView2Settings.IsNonClientRegionSupportEnabled Property

Win32/C++

• ICoreWebView2CompositionController4

  • ICoreWebView2CompositionController4::add_NonClientRegionChanged
  • ICoreWebView2CompositionController4::GetNonClientRegionAtPoint
  • ICoreWebView2CompositionController4::QueryNonClientRegion
  • ICoreWebView2CompositionController4::remove_NonClientRegionChanged

• ICoreWebView2NonClientRegionChangedEventArgs

  • ICoreWebView2NonClientRegionChangedEventArgs::get_RegionKind

• ICoreWebView2NonClientRegionChangedEventHandler

• ICoreWebView2RegionRectCollectionView

• ICoreWebView2Settings9

  • ICoreWebView2Settings9::get_IsNonClientRegionSupportEnabled
  • ICoreWebView2Settings9::put_IsNonClientRegionSupportEnabled

• COREWEBVIEW2_NON_CLIENT_REGION_KIND enum

  • COREWEBVIEW2_NON_CLIENT_REGION_KIND_CAPTION
  • COREWEBVIEW2_NON_CLIENT_REGION_KIND_CLIENT
  • COREWEBVIEW2_NON_CLIENT_REGION_KIND_NOWHERE

FailureSourceModulePath property

Added the FailureSourceModulePath property to the ProcessFailedEventArgs type, to specify the full path of the module that caused the crash in cases of Windows code integrity failures - that is, when a process exited with STATUS_INVALID_IMAGE_HASH.

Previous phase: FailureSourceModulePath property in Prerelease SDK 1.0.2470-prerelease, for Runtime 124 (Mar. 25, 2024).

.NET/C#

• CoreWebView2ProcessFailedEventArgs Class:
  • CoreWebView2ProcessFailedEventArgs.FailureSourceModulePath Property

WinRT/C#

• CoreWebView2ProcessFailedEventArgs Class:
  • CoreWebView2ProcessFailedEventArgs.FailureSourceModulePath Property

Win32/C++

• ICoreWebView2ProcessFailedEventArgs3
  • ICoreWebView2ProcessFailedEventArgs3::get_FailureSourceModulePath

Bug fixes

• The .NET assemblies for WinForms and WPF are now shipped with optimization enabled. (Issue #4409)

See also

• Runtime 123.0.2420.47 (Mar. 25, 2024)
• Release notes for WebView2
  • Release notes for the WebView2 Runtime
  • Release notes for WebView2 SDKs