DotNetBrowser 1.8.1

The new version lists the following features and improvements:

DOM API update, which brings the possibility to modify DOM: create, append, insert, replace and remove DOM nodes.
Ability to get the DOM node at the particular location on the page.
Ability to emulate custom DOM events for the specific DOM elements.
Mute Audio API. This API allows to mute all audio output for the particular Browser instance. Also, it is possible to determine if the browser is currently muted or playing audio.
Ability to customize the filename for the native process. Now it is possible to set the custom name for DotNetBrowser.Chromium.exe and all native process instances will be subsequently renamed.
Back-forward navigation history list support. Now it is possible to navigate to the particular entry in the back-forward navigation history and even remove some entries from the history.
Browser.Loading property which allows to determine whether browser is currently loading something.
Editor commands support. Editor commands are the commands for text manipulation when editing in a text field, text area or WYSIWYG editor. Also these commands include more common commands like Cut, Copy, Paste, SelectAll, Undo, Redo, which can be executed for the frame in the loaded web page.
Web storage API. Now it is possible to access local or session web storage and create, store, find and remove key/value pairs in it.
Ability to get selected text or HTML for the frame with a specific ID.
Ability to pause, resume and cancel downloads.
Password Manager update. Now it is possible to be informed about the password update events (when the user enters a new password for the previously saved login).
Added RenderGone event. This event allows to detect unexpected render process termination and relaunch it by loading the same URL once more.

And the following issues have been fixed in this update:

XPath iterator behavior. In the previous versions, if XPath request returned iterator, and then the nodes were modified, the iterator just stopped working. Now it throws a proper exception that informs that the document has been mutated since the result was returned.
Frame ID validation. In previous version, any operations related to a frame with a specific ID were able to accept an invalid frame ID. Now each operation checks if the frame with the specified ID exists.
Access violation exception on 64-bit platforms on creating Browser instance. This issue was reproducible in 64-bit environment only and appeared from time to time, now it is resolved.
Fixed a native process crash in multi-threaded environment.
Resolved possible crashes when selecting the first SSL certificate in the list or canceling selection in the DialogHandler.onSelectCertificate() method.

Go Top