You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: specs/SensitivityLabel.md
+10-12Lines changed: 10 additions & 12 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,28 +2,26 @@ Sensitivity label support for Webview2
2
2
===
3
3
4
4
# Background
5
-
Web pages may contain content with sensitive information. Such information can be identified using data loss protection methods. The purpose of this API is to provide sensitivity label information, communicated by web pages through the [Page Interaction Restriction Manager](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PageInteractionRestrictionManager/explainer.md), to the host application. This enables the host application to be informed of the presence of sensitive content.
5
+
Web pages may contain content with sensitive information. Such information can be identified using data loss protection (DLP) methods. The purpose of this API is to provide sensitivity label information, communicated by web pages through the [PageInteractionRestrictionManager](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PageInteractionRestrictionManager/explainer.md), to the host application. This enables the host application to be informed of the presence of sensitive content.
6
6
7
7
## Note about .NET/WinRT projection
8
-
The work to project this API to .NET and WinRT are yet to be completed. Overall
9
-
usage of this API is expected to be uncommon. There are no known asks for
10
-
this.
8
+
The work to project this API to .NET and WinRT are yet to be completed.
11
9
12
10
# Description
13
11
14
-
We propose introducing a SensitivityLabelChanged event to the CoreWebView2 object, enabling applications to monitor changes in sensitivity labels within hosted content. This functionality is restricted to domains explicitly included in an allow list configured by the application. The allow list can be set at the profile level, thereby enabling the Page Interaction Restriction Manager for content within specified domains. By default, the allow list is empty, preventing hosted content from transmitting sensitivity label information.
12
+
This API introduces a SensitivityLabelChanged event to the CoreWebView2 object, enabling applications to monitor changes in sensitivity labels within hosted content. This functionality is restricted to domains explicitly included in an allow list configured by the application. The allow list can be set at the profile level, thereby enabling the Page Interaction Restriction Manager for content within specified domains. By default, the allow list is empty, preventing hosted content from transmitting sensitivity label information.
15
13
16
14
The core features of this proposal are as follows:
17
-
* Configure the allowlist filter for Page Interaction Restriction Manager at the profile level.
18
-
* After the setup, the `Page Interaction Restriction Manager` is available on allowlisted pages. Content can send sensitivity labels to the platform via the API.
15
+
* Configure the allow list filter for Page Interaction Restriction Manager at the profile level.
16
+
* After the setup, the `Page Interaction Restriction Manager` is available on pages in the allow list. Content can send sensitivity labels to the platform via the API.
19
17
* When a label changes, an event is raised by WebView2 to hosted app with all the labels on that page.
20
18
* Sensitivity labels are cleared when navigating away from the current WebView.
21
19
22
20
# Examples
23
21
24
-
## Setting Up an Allowlist
22
+
## Setting up an allow list
25
23
26
-
Configure the PageInteractionRestrictionManager allowlist to enable DLP functionality on trusted domains.
24
+
Configure the PageInteractionRestrictionManager allow list to enable DLP functionality on trusted domains.
27
25
28
26
```cpp
29
27
voidConfigureAllowlist()
@@ -34,7 +32,7 @@ void ConfigureAllowlist()
34
32
35
33
auto stagingProfile3 = profile.try_query<ICoreWebView2StagingProfile3>();
0 commit comments