Posted on April 27, 2017
With this release we are pleased to introduce the long awaited upgrade. Now DotNetBrowser runs on a more powerful browser engine – Chromium 55.0.2883.87. But we did not stop there, check the full list of enhancements we delivered with this update:
- Implemented Chromium sandbox support. By default, Chromium sandbox is disabled to keep the behavior of previous DotNetBrowser versions. To enable sandbox, use the approach described in the following article.
- The library now supports HTML5 transparent background. See example.
- Added the
OnPreviewKeyDownevent support in WinForms heavyweight rendering mode.
- Added support of the proper key modifiers for the keyboard events in WinForms heavyweight rendering mode.
- Implemented an ability to embed WPFBrowserView into WinForms ElementHost. See example.
Here’s what has been resolved in this update:
- The issue with MS Visual Studio 2013 crash when adding DotNetBrowser reference to the VB.NET project.
- The issue related to using different proxy settings in different
Browserinstances. In the new version, the functionality that allows configuring proxy settings for each
Browserinstance separately works properly.
- The blacklisting issue for the
PasswordSubmittedevent is no longer created for already blacklisted websites.
- The blurred fonts issue in the heavyweight rendering mode for both WinForms and WPF. Now fonts in the heavyweight rendering mode are rendered exactly as in Google Chrome.
- The issue when some CSS cursors aren’t displayed in the heavyweight rendering mode for both WinForms and WPF.
- The issue with memory leak when creating and disposing WPF control multiple times.
- The Browser initialization issue for the case when current thread culture is
- MS Visual Studio Designer errors for the
Subscribe to @DotNetBrowser on Twitter to get notified of the library updates.