ICoreWebView2Frame5

Undocumented in source.
version(Windows && inline_webview2_bindings && all)
interface ICoreWebView2Frame5 : ICoreWebView2Frame4 {
static const
GUID iid;
}

Members

Functions

get_FrameId
HRESULT get_FrameId(UINT32* id)

The unique identifier of the current frame. It's the same kind of ID as with the FrameId in CoreWebView2 and via CoreWebView2FrameInfo.

Inherited Members

From ICoreWebView2Frame4

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

Share a shared buffer object with script of the iframe 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