Release Notes for the WebView2 SDK

These Release Notes provide information about new features and bug fixes that are included in the WebView2 Release SDK and the WebView2 Prerelease SDK.

Release Date: March 10, 2025

NuGet package for WebView2 SDK 1.0.3124.44

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 134.0.3124.44 or higher.

No additional APIs have been promoted to Stable and added in this Release SDK.

• Extensions won't get disabled in WebView2 by using AddBrowserExtensionAsync, regardless of whether developer mode is on. (Issue #5113)
• Disabled background update of network time. (Issue #5047)
• Fixed the download popup not being displayed when target="_blank". (Issue #5063)

Release Date: March 10, 2025

NuGet package for WebView2 SDK 1.0.3171-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 135.0.3171.0 or higher.

No Experimental APIs have been added in this Prerelease SDK.

No APIs have been promoted from Experimental to Stable in this Prerelease SDK.

• Fixed host object async method exception handling. (Issue #3402)
• Fixed documentation for CoreWebVIew2.Navigate. (Issue #5091)

• Fixed an "Add to Chrome" store installation regression.
• Fixed folder uploads in UWP and WinUI. (Issue #3275)
• Extensions won't get disabled in WebView2 by using AddBrowserExtensionAsync, regardless of whether developer mode is on. (Issue #5113)
• Disabled background update of network time. (Issue #5047)
• Fixed the download popup not being displayed when target="_blank". (Issue #5063)

• Fixes a crash that could occur when the Garbage Collector calls Finalize on a thread other than the main thread.

Release Date: February 10, 2025

NuGet package for WebView2 SDK 1.0.3065.39

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 133.0.3065.39 or higher.

No additional APIs have been promoted to Stable and added in this Release SDK.

• Added the missing Close button in the Download flyout.
• Fixed a race condition that occurred when the Web Request Response event never occurs.

Release Date: February 10, 2025

NuGet package for WebView2 SDK 1.0.3116-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 134.0.3116.0 or higher.

No Experimental APIs have been added in this Prerelease SDK.

No APIs have been promoted from Experimental to Stable in this Prerelease SDK.

• Added the missing Close button in the Download flyout.
• Fixed a race condition that occurred when the Web Request Response event never occurs.

• Fixed .NET and Win32 documentation of the CoreWebView2Find.FindNext method that incorrectly mentioned FindPrevious. The method summary now mentions FindNext instead. (Issue #5059)

Release Date: January 20, 2025

NuGet package for WebView2 SDK 1.0.2957.106

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 132.0.2957.106 or higher.

The following APIs have been promoted to Stable and are now included in this Release SDK.

The WebView2CompositionControl prevents the WebView2 control from being the topmost layer in a WPF app and obscuring any WPF elements. Microsoft.Web.WebView2.Wpf.WebView2CompositionControl is a drop-in replacement for the standard WPF WebView2 control. Both the WebView2 control and WebView2CompositionControl implement the Microsoft.Web.WebView2.Wpf.IWebView2 interface. Both of them derive from FrameworkElement, as follows:

• FrameworkElement -> HwndHost -> WebView2.
• FrameworkElement -> Control -> WebView2CompositionControl.

Background: If you're building a Windows Presentation Foundation (WPF) app and using the WebView2 control, you may find that your app runs into "airspace" issues, where the WebView2 control is always displayed on top, hiding any WPF elements in the same location, even if you try to specify the WPF elements to be above the WebView2 control (using visual tree order or the z-index property, for example).

This issue occurs because the WPF control uses the WPF HwndHost to host the Win32 WebView2 control, and HwndHost has an issue with airspace.

See also:

• Mitigating Airspace Issues In WPF Applications
• WPF Airspace - WebView2CompositionControl - Spec.

• Fixed a regression where display changes can cause WebView2 to render smaller than the app window.

• Fixed an issue in the WPF WebView2CompositionControl where it's not displayed if it's initialized with size (0,0), such as when it's initialized in a TabItem of a TabControl. (Issue #4941)

Release Date: January 24, 2025

NuGet package for WebView2 SDK 1.0.3079-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 134.0.3079.0 or higher.

The following Experimental APIs have been added in this Prerelease SDK.

The Find API allows you to programmatically control Find operations, and enables adding the following functionality to your app:

• Customize Find options, including Find Term, Case Sensitivity, Word Matching, Match Highlighting, and Default UI Suppression.
• Find text strings and navigate among them within a WebView2 control.
• Programmatically initiate Find operations, and navigate Find results.
• Suppress the default Find UI.
• Track the status of Find operations.

There are known issues with the Find API for PDF documents. When you view a PDF document within a WebView2 control, the Find feature currently only provides the first index and the number of matches found. For example, if the string occurs three times in a PDF, the UI would say 1/3 and would not support programmatically calling Next or Previous. We are actively investigating these issues, and we encourage you to report any problems you encounter, by using the WebView2Feedback repo.

The DragStarting API overrides the default drag and drop behavior when running in visual hosting mode. The DragStarting event notifies your app when the user starts a drag operation in the WebView2, and provides the state that's necessary to override the default WebView2 drag operation with your own logic.

• Use DragStarting on the ICoreWebView2ExperimentalCompositionController6 to add an event handler that's invoked when the drag operation is starting.
• Use ICoreWebView2ExperimentalDragStartingEventArgs to start your own drag operation.
  • Use the GetDeferral method to execute any async drag logic and call back into the WebView at a later time.
  • Use the Handled property to let the WebView2 know whether to use its own drag logic.

The FrameCreatedEvent API supports nested iframes, such as recording the navigation history for a second-level iframe. Without this API, WebView2 only tracks first-level iframes, which are the direct child iframes of the main frame. Using this API, your app can subscribe to the nested iframe creation event, giving the app access to all properties, methods, and events of CoreWebView2Frame for the nested iframe.

Use this API to manage iframe tracking on a page that contains multiple levels of iframes. You can choose to track any of the following:

• Only the main page and first-level iframes (the default behavior).
• A partial WebView2 frames tree with specific iframes of interest.
• The full WebView2 frames tree.

The DefaultBackgroundColor API allows users to set the DefaultBackgroundColor property at initialization. This prevents a disruptive white flash during the WebView2 loading process.

The following APIs have been promoted from Experimental to Stable in this Prerelease SDK.

The WebView2CompositionControl prevents the WebView2 control from being the topmost layer in a WPF app and obscuring any WPF elements. Microsoft.Web.WebView2.Wpf.WebView2CompositionControl is a drop-in replacement for the standard WPF WebView2 control. Both the WebView2 control and WebView2CompositionControl implement the Microsoft.Web.WebView2.Wpf.IWebView2 interface. Both of them derive from FrameworkElement, as follows:

• FrameworkElement -> HwndHost -> WebView2.
• FrameworkElement -> Control -> WebView2CompositionControl.

Background: If you're building a Windows Presentation Foundation (WPF) app and using the WebView2 control, you may find that your app runs into "airspace" issues, where the WebView2 control is always displayed on top, hiding any WPF elements in the same location, even if you try to specify the WPF elements to be above the WebView2 control (using visual tree order or the z-index property, for example).

This issue occurs because the WPF control uses the WPF HwndHost to host the Win32 WebView2 control, and HwndHost has an issue with airspace.

See also:

• Mitigating Airspace Issues In WPF Applications
• WPF Airspace - WebView2CompositionControl - Spec.

• Fixed a regression where display changes can cause WebView2 to render smaller than app window.
• Enabled the IsolateSandboxedIframes upstream feature for WebView2.
• Prevented deleting a service worker when the version changes.
• The CleanUpSome API in Hostobject now only does garbage collection for the full heap. CleanUpSome has been removed from the V8 engine.
• Fixed a regression of AreBrowserAcceleratorKeysEnabled. (Issue #5033)
• Fixed a bug where IsDefaultDownloadDialogOpenChanged wasn't triggered when a dialog is closed by using the keyboard. (Issue #4807)

• Fixed an issue in the WPF WebView2CompositionControl where it's not displayed if it's initialized with size (0,0), such as when it's initialized in a TabItem of a TabControl. (Issue #4941)

Release Date: November 18, 2024

NuGet package for WebView2 SDK 1.0.2903.40

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 131.0.2903.40 or higher.

The following APIs have been promoted to Stable and are now included in this Release SDK.

Added a new ScreenCaptureStarting event. This event is raised whenever the WebView2 and/or iframe that corresponds to the CoreWebView2Frame (or to any of its descendant iframes) requests permission to use the Screen Capture API before the UI is shown. The app can then block the UI from being displayed, or allow the UI to be displayed.

• Allowed the Download dialog to receive initial focus on launch.

• The Microsoft Edge WebView2 Runtime is no longer listed in Windows Settings > Apps > Installed apps, because it is a persistent system component.

Release Date: November 18, 2024

NuGet package for WebView2 SDK 1.0.2950-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 132.0.2950.0 or higher.

No Experimental APIs have been added in this Prerelease SDK.

No APIs have been promoted from Experimental to Stable in this Prerelease SDK.

• Allowed the Download dialog to receive initial focus on launch.
• Fixed a crash while cancelling navigation to certain sites in FrameNavigationStarting. (Issue #4843)
• Postponed customizing the context menu when the touch selection menu is being displayed. (Issue #4737)

• Added Arm64ec support.
• Fixed an issue where WebView2 running in "Window to Visual" mode couldn't receive accelerator input.

Release Date: October 21, 2024

NuGet package for WebView2 SDK 1.0.2849.39

For full API compatibility, this Release version of the WebView2 SDK requires WebView2 Runtime version 130.0.2849.39 or higher.

The following APIs have been promoted to Stable and are now included in this Release SDK.

Added a new SaveFileSecurityCheckStarting event. Your app can register a handler on this event to get the file path, filename extension, and document origin URI information. You can then apply your own rules to do actions such as the following:

• Allow saving the file without presenting a default security-warning UI about the file-type policy.
• Cancel the saving.
• Create your own UI to manage runtime file-type policies.

• Fixed a Download dialog focus issue when pressing Tab or Shift+Tab to switch into the Webview2 control.

• Using CoreWebView2.AddWebResourceRequestedFilter without a CoreWebView2WebResourceRequestSourceKinds parameter is now deprecated. See the .NET CoreWebView2.AddWebResourceRequestedFilter Method.
• Added the .NET 8 TargetFramework for C# WinRT, enabled AOT (ahead-of-time) compatibility, and disabled runtime marshalling.

Release Date: October 21, 2024

NuGet package for WebView2 SDK 1.0.2895-prerelease

For full API compatibility, this Prerelease version of the WebView2 SDK requires the WebView2 Runtime that ships with Microsoft Edge version 131.0.2895.0 or higher.

The following Experimental APIs have been added in this Prerelease SDK.

Added a new RestartRequested event. The RestartRequested event is raised whenever WebView2 needs to restart to apply updates or configuration changes. You can use this API to detect when WebView2 needs to restart, and take appropriate actions. The Priority property of the RestartRequested event arguments indicates the priority of the restart request:

• High indicates that the app should prompt users to restart as soon as possible.
• Normal indicates that the app should remind users to restart, on a best-effort basis.

The following APIs have been promoted from Experimental to Stable in this Prerelease SDK.

Added a new ScreenCaptureStarting event. This event is raised whenever the WebView2 and/or iframe that corresponds to the CoreWebView2Frame (or to any of its descendant iframes) requests permission to use the Screen Capture API before the UI is shown. The app can then block the UI from being displayed, or allow the UI to be displayed.

Added a new SaveFileSecurityCheckStarting event. Your app can register a handler on this event to get the file path, filename extension, and document origin URI information. You can then apply your own rules to do actions such as the following:

• Allow saving the file without presenting a default security-warning UI about the file-type policy.
• Cancel the saving.
• Create your own UI to manage runtime file-type policies.

• Fixed Arm64 incompatibility with WindowsAppSDK 1.6.
• Removed extra WebView2Loader.dll in WinAppSDK case.
• Using CoreWebView2.AddWebResourceRequestedFilter without a CoreWebView2WebResourceRequestSourceKinds parameter is now deprecated. See the .NET CoreWebView2.AddWebResourceRequestedFilter Method.

• About Release Notes for the WebView2 SDK
• Archived Release Notes for the WebView2 SDK
• Overview of WebView2 APIs - outlines many of the APIs, by feature area, that are in Release SDK packages.
• Contacting the Microsoft Edge WebView2 team
• Release notes for Microsoft Edge web platform