DotNetBrowser 4.3.2

Breaking changes

Windows registry extensions

On Windows, DotNetBrowser no longer installs extensions registered in the Windows registry. This prevents an embedded browser from loading extension code that the application did not request.

Applications that need an extension should install it through their own application-controlled extension setup instead of relying on Chrome extension registry entries.

Chromium 154.0.8037.58

We upgraded Chromium to a newer version, which introduces 166 security fixes.

See the Chromium release announcements for more details.

Quality enhancements

Fixed memory growth in the .NET process when an application made repeated DOM or other calls from a long-running event handler.
Fixed a memory leak that kept disposed page contexts, DOM contexts, and JS contexts in memory after navigation.
Fixed a Chromium process crash that could occur after a web page started a Presentation API request and the application answered StartPresentationHandler.
Compressed response bodies written by UrlRequestJob in InterceptRequestResponse are now decoded according to the Content-Encoding header. This lets intercepted HTML, scripts, and styles load as decoded content instead of raw compressed bytes.
Fixed Browser.DevTools.Show() on macOS so the DevTools window is visible again.
Disabled network requests from Chromium’s on-device AI component to Google’s update service.
Improved native input handling for complex IMEs on Windows and Linux.

Download DotNetBrowser 4.3.2

Please share your email with us, and we'll send you download instructions.

Please check your inbox.

We were unable to send the email. Please try again.

If you are a registered customer you don’t need to do anything to use this update.

If you would like to evaluate the product, you need an evaluation license.

Get free 30-day trial