DotNetBrowser

Version 1.16 of DotNetBrowser comes with a whole bunch of useful changes:

HiDPI Displays

In this version, we are glad to introduce the HiDPI Displays support which allows using all DPI-aware modes. The BrowserView control is compatible with various DPI awareness modes and renders HTML content with respect to the scale factor.

See this article for more details.

FIPS-compliance

We are FIPS-compliant now! Starting from the version 1.16 it is possible to use DotNetBrowser in the environments where the Federal Information Processing Standard restriction is enabled.

Improvements:

• The render channel initialization now works better. It was achieved by preventing script context creation until the client-side Browser instance is created.
• Now you can specify the type of the printed document by means of the Printing API.
• The issue when a drop-down list is displayed inside the BrowserView in the heavyweight rendering mode.
• If you don’t want the library to generate and store crash dumps, you can now set BrowserPreferences.CrashDumpDir as an empty string.

Fixed issues:

• The KeyDown event being unable to subscribe in WinForms in the lightweight rendering mode.
• The MouseMove, the MouseEnter and the MouseExit events not forwarded in WinForms in the heavyweight rendering mode.
• The native crash on specific video cards and VMs.
• A webpage content being rendered with wrong height and width in the lightweight rendering mode.

Request evaluation licence
Download DotNetBrowser 1.16

Release date: June 29, 2018

This issue was related to the specific case when DotNetBrowser launched on Virtual Machines or used Remote Desktop Connection to the machine which did not have any connected display. In Chromium 64 were introduced the modified libraries (swiftshader/libEGL.dll and swiftshader/libGLESv2.dll), so we included these libraries into our release to fix the mentioned case.