After reading the license of the fixed version WebView2 runtime and this document I realized that WebView2 is sending data to Microsoft by default. This is bad because it means that any application using WebView2 as-is must make its users aware of this data collection and request consent.
There are three kinds of data WebView2 collects and sends to MS:
The sending of the diagnostic data can be controlled by a global Windows setting. But the other two can only be set programmatically using the ICoreWebView2Settings and ICoreWebView2EnvironmentOptions3 interfaces.
Since there is no easy way to access those interfaces from client code I propose to disable the SmartScreen and crash reporting options by default and optionally allow client code to enable them again after asking the user.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I agree with disabling them by default, please consider making a PR doing this after testing that it actually works. TIA!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Closed #23978 as completed via cd350c7.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
According to the documentation, "When IsCustomCrashReportingEnabled is set to true, Windows won't send crash data to Microsoft endpoint." This bugfix is setting it to false by default.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
This is very counterintuitive but the documentation indeed seems to indicate that the meaning of this field is contrary to what could be expected. @TcT2k Should we set it to true instead?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
Well the documentation seems very clear. But I agree that its very counterintuitive.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
I hoped that you might have some experience with how it actually works, but if not, let's indeed change this, thanks @mattfeest.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()