Posted on August 31, 2018
Summer months were quite fruitful for DotNetBrowser. Here comes several new features:
Default zoom level
It is now possible to set the default zoom level for the
BrowserContext instance during its creation. This property allows you to specify the default zoom level for all browsers which use the same context. All pages which are loaded through these
Browser instances will have the specified zoom level from the start.
Read more on using this property here.
Mouse input simulation
The new version provides an alternative way to simulate mouse input through the
Browser instance. You can call the
MouseWheel methods directly from the
Browser instance. For detailed instructions, please see Simulating Mouse Input.
Upload progress notifications
Now it’s possible to subscribe to the
Browser.UploadProgressChanged event and receive notifications about uploading progress. See the article for more details.
WinFormsBrowserView layout changing
In DotNetBrowser 1.17, the
WinFormsBrowserView.Dock property was set to the
DockStyle.None value by default. Please, make sure your application fits this update. Please read about how this change may affect your application in the article.
- We have improved the DotNetBrowser performance when the logging is disabled.
- Made it possible to load URL with specified frame id. See the
- You can also access the
BrowserView.Focusedproperty in the new version.
- DotNetBrowser crashing with the OutOfMemory exception caused by logging.
- DotNetBrowser crashing if started under an unprivileged user in the Windows Server environments.
- Incorrect rendering in the lightweight rendering mode with display scaling settings more than 100%.
- DotNetBrowser in the lightweight rendering mode not forward focusing out of the
- Failing to register a new protocol handler due to asynchronous implementation.
ImageProvider.GetImage()hanging during debug.
- DotNetBrowser crashing during initialization with the inner exception: “Unable to find an entry point named ‘GetDpiForWindow’ in DLL ‘user32.dll’.”
- Failing to restore focus after minimizing-restoring of the window.
- The IntelliSense issue related to arguments renaming.
- The IntelliSense issue with missed
WPFBrowserViewin heavyweight mode being invisible on startup.