Sep 14 2020 10:36 AM
Sep 14 2020 10:36 AM
I see that after the update of Edge Beta to v86, the policies set in registry no longer work for Webview2-based browsers. E.g. I can freely download files on the browser despite DownloadRestrictions set to 3 (block all).
Yet, there is no such problem with v85 (Stable channel), or when using standalone Edge Beta v86, policies are respected.
Is this a bug?
Sep 14 2020 03:05 PM
@alexbond , this is a change introduced in recent release, see Release Notes for Microsoft Edge WebView2 for Win32, WPF, and WinForms - Microsoft Edge Development ....
Sep 14 2020 03:13 PM - edited Sep 14 2020 03:15 PMSolution
Specifically to your comment about "Webview2-based browsers", these apps that are built on top of the browser. We recommend developers owning these apps to expose their own policies to control WebView2 download behavior, or admins can block those apps from installing if they are malicious.
Sep 14 2020 06:45 PM
Sep 14 2020 10:22 PM
@alexbond download is one of the scenarios we're looking at actually. I'd encourage following https://github.com/MicrosoftEdge/WebViewFeedback/issues/419.
There isn't a WebView2 API per se today that blocks download, but before we expose one, there is a workaround. You can use CallDevToolsProtocolMethod (https://docs.microsoft.com/en-us/microsoft-edge/webview2/reference/win32/0-9-622/icorewebview2#calld...) to call Chrome DevTool Protocol APIs (https://chromedevtools.github.io/devtools-protocol/) from WebView2, and Browser.setDownloadBehavior (https://chromedevtools.github.io/devtools-protocol/tot/Browser/#method-setDownloadBehavior) lets you block download.
Sep 15 2020 10:01 AM
Thank you @liminzhu ,
that's very helpful. Can you also help me understand of the ways I can be informed about upcoming/planned disrupting changes like this with Webview2? This is impacting our company business and I'd want to avoid it when possible. Is there anything besides https://docs.microsoft.com/en-us/microsoft-edge/webview2/releasenotes I can look at?
Also, note that the above release notes state that browser policies disconnected in WebView v0.9.622.
Yet it's clear that this change is unrelated to WebView2 version (e.g. policy disconnect still happens with v0.9.430), and is rather tied to Edge v86 release with any compatible WebView2. You might want to correct the page to avoid confusion there.
Sep 20 2020 03:21 PM
@alexbond besides release notes, we recently made https://github.com/MicrosoftEdge/WebView2Announcements where you can subscribe and get notifications on announcements, API proposals, etc. We are making changes like this during preview so that we don't have to make them post GA.
> Yet it's clear that this change is unrelated to WebView2 version (e.g. policy disconnect still happens with v0.9.430), and is rather tied to Edge v86 release with any compatible WebView2. You might want to correct the page to avoid confusion there.