We would like to support a subset of third party WebExtensions in our WebView2 based browser. We do not plan to use any of the existing stores (such as Edge Add-ons Store/Chrome Web Store), but rather ship extensions with the browser or download them from our own servers.
Since we won't have a full control over the extension's code (unlike Support for UI-less WebExtensions) WebView2 would need to provide us with a way to support UI-related APIs (such as "tabs" and "contextMenus").
Apple is currently in the process of adding extension support to their WKWebView, enabling the host application to communicate such info as tab and window data to the extensions - e.g. _WKWebExtensionTab.h and _WKWebExtensionWindow.h.
We would like to support a subset of third party WebExtensions in our WebView2 based browser. We do not plan to use any of the existing stores (such as Edge Add-ons Store/Chrome Web Store), but rather ship extensions with the browser or download them from our own servers.
Since we won't have a full control over the extension's code (unlike Support for UI-less WebExtensions) WebView2 would need to provide us with a way to support UI-related APIs (such as "tabs" and "contextMenus").
Apple is currently in the process of adding extension support to their WKWebView, enabling the host application to communicate such info as tab and window data to the extensions - e.g. _WKWebExtensionTab.h and _WKWebExtensionWindow.h.