Skip to content

Commit e1d00ba

Browse files
authored
Update IsSmartScreenRequired.md
1 parent e41b740 commit e1d00ba

File tree

1 file changed

+3
-1
lines changed

1 file changed

+3
-1
lines changed

specs/IsSmartScreenRequired.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,10 +15,12 @@ In this document we describe the new setting.
1515
# Description
1616
You can use CoreWebView2Settings.IsReputationCheckingRequired to control SmartScreen. SmartScreen is enabled or disabled per browser process, so all WebView2 applications sharing the same user data folder path also share SmartScreen being enabled or disabled.
1717
If CoreWebView2Setting.IsReputationCheckingRequired is true for any CoreWebView2 using the same user data folder, then SmartScreen is enabled. If CoreWebView2Setting.IsReputationCheckingRequired is false for all CoreWebView2 using the same user data folder, then SmartScreen is disabled.
18-
The default value for `IsReputationCheckingRequired` is true. When a new CoreWebview2 is created, the SmartScreens of all CoreWebviews using the same user data folder are reset to true.
18+
The default value for `IsReputationCheckingRequired` is true. When creating a new CoreWebVIew2, if it is not set CoreWebView2Settings.IsReputationCheckingRequired, the SmartScreen state of all CoreWebView2s using the same user data folder will be reset to true when the new CoreWebView2 is navigated or downloaded.
1919

2020
Changes to `IsReputationCheckingRequired` take effect on the next navigation or download.
2121

22+
If the option `--disable-features=msSmartScreenProtection` is specified when CoreWebView2Environment is created, then SmartScreen cannot be set through CoreWebView2Settings.IsReputationCheckingRequired. In this scenario, SmartScreen is always turned off.
23+
2224

2325
# Examples
2426
```cpp

0 commit comments

Comments
 (0)