The OpenD Programming Language

ICoreWebView2_18

Undocumented in source.

Members

Functions

add_LaunchingExternalUriScheme
HRESULT add_LaunchingExternalUriScheme(ICoreWebView2LaunchingExternalUriSchemeEventHandler eventHandler, EventRegistrationToken* token)

Add an event handler for the LaunchingExternalUriScheme event. The LaunchingExternalUriScheme event is raised when a navigation request is made to a URI scheme that is registered with the OS. The LaunchingExternalUriScheme event handler may suppress the default dialog or replace the default dialog with a custom dialog.

remove_LaunchingExternalUriScheme
HRESULT remove_LaunchingExternalUriScheme(EventRegistrationToken token)

Remove an event handler previously added with add_LaunchingExternalUriScheme.

Inherited Members

From ICoreWebView2_17

PostSharedBufferToScript
HRESULT PostSharedBufferToScript(ICoreWebView2SharedBuffer sharedBuffer, COREWEBVIEW2_SHARED_BUFFER_ACCESS access, LPCWSTR additionalDataAsJson)

Share a shared buffer object with script of the main frame in the WebView. The script will receive a sharedbufferreceived event from chrome.webview. The event arg for that event will have the following methods and properties: getBuffer(): return an ArrayBuffer object with the backing content from the shared buffer. additionalData: an object as the result of parsing additionalDataAsJson as JSON string. This property will be undefined if additionalDataAsJson is nullptr or empty string. source: with a value set as chrome.webview object. If a string is provided as additionalDataAsJson but it is not a valid JSON string, the API will fail with E_INVALIDARG. If access is COREWEBVIEW2_SHARED_BUFFER_ACCESS_READ_ONLY, the script will only have read access to the buffer. If the script tries to modify the content in a read only buffer, it will cause an access violation in WebView renderer process and crash the renderer process. If the shared buffer is already closed, the API will fail with RO_E_CLOSED.

Meta