Posted on August 8, 2016

DotNetBrowser 1.8

The main change in DotNetBrowser 1.8 is upgrade of its Chromium engine to version 51.0.2704.106.

In November 2015 Google announced the end of Chrome/Chromium’s support for Windows XP, as well as Windows Vista, and Mac OS X 10.6, 10.7, and 10.8, since these platforms are no longer actively supported by Microsoft and Apple. Starting with Google Chrome/Chromium 50, these platforms are no longer supported at all. Since DotNetBrowser 1.8 is based on Chromium 51, support of these platforms has been dropped as well.

The new version also contains several new features and improvements:

• Improved the process of creating a screenshot of the complete web page in the lightweight mode. We have added the OnRedraw event to the DrawingView, and it resolves the threading issue with OnRepaint event. The OnRedraw event is fired on the main event thread, so the captured image can be obtained in the same thread and there is no need to invoke GetImage() in the main thread.
• Added possibility to modify upload data. Now API allows to access and modify POST/PUT/PATCH upload data before sending it to a web server.
• Added mouse simulation support. Now it is possible to simulate mouse movement, scroll and clicks even for an off-screen Browser.
• Added native crash handler. Now it is possible to be notified about the native process crash. In previous versions, the dump file was generated silently on native process crash and the component simply stopped functioning. The crash handler provides a possibility for your application to be notified about this. As a result, your application can stop working with the crashed component.

The following reported issues were fixed in this release:

• Fixed default file chooser. Now it is capable to recognize acceptable file types. The default implementation of the file chooser in previous versions was not able to recognize acceptable file types and allowed to accept files of any type.
• Fixed mouse movement latency. In previous versions, you might notice that the component is working slower if a significant number of mouse events (clicks or movements) is generated. In the new version, the number of mouse events will not cause latency in component rendering.