Posted on November 27, 2018
The new version of DotNetBrowser got more flexible and stable due to the following changes:
Browser.Dispose(bool checkBeforeUnload) Implemented
Due to this method, it got possible to invoke the
DialogHandler.OnBeforeUnload method which is fired if the web page contains the
This property provides a meaningful description of the file extensions accepted by the file chooser. This information comes from the accept attribute of the input HTML element with the
- Now DotNetBrowser is able of managing download process even if the
Browserinstance which initiated the download activity has been disposed.
- Starting with this update you can set the specific bitmap scaling mode for a
WPFBrowserViewinstance in the lightweight rendering mode.
- We also improved the memory usage in the Chromium binaries verification functionality.
- The NullReferenceException exception which is thrown when disposing the
WinFormsBrowserViewinstance in the heavyweight rendering mode.
- The ArgumentOutOfRangeException exception which is thrown when setting the
- Inability to use a custom client certificate if it already exists in the certificate storage.
- The UnauthorizedAccessException exception which is thrown if the
LoggerProvider.Instance.OutputFileproperty is set to a path which has no write access.
- The OutOfMemoryException exception which is thrown during verification of the Chromium binaries.
- Inability to navigate with the arrow keys inside a drop-down list in the lightweight rendering mode.
CertificateVerifyParams.VerifyFlagsproperty always returning null.
- The issue with the relative path in the
Subscribe to @DotNetBrowser on Twitter to get notified of the library updates.
Subscribe to our RSS feed to get instant updates on new releases.