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
+75-77Lines changed: 75 additions & 77 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2,23 +2,39 @@ 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 (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.
5
+
Web pages may contain content with sensitive information. Such information can
6
+
be identified using data loss protection (DLP) methods. The purpose of this API
7
+
is to provide sensitivity label information, communicated by web pages through
8
+
the [PageInteractionRestrictionManager](https://github.com/MicrosoftEdge/MSEdgeExplainers/blob/main/PageInteractionRestrictionManager/explainer.md),
9
+
to the host application. This enables the host application to be informed of the
10
+
presence of sensitive content.
6
11
7
12
# Description
8
13
9
-
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.
14
+
This API introduces a SensitivityLabelChanged event to the CoreWebView2 object,
15
+
enabling applications to monitor changes in sensitivity labels within hosted
16
+
content. This functionality is restricted to domains explicitly included in an
17
+
allow list configured by the application. The allow list can be set at the
18
+
profile level, thereby enabling the Page Interaction Restriction Manager for
19
+
content within specified domains. By default, the allow list is empty,
20
+
preventing hosted content from transmitting sensitivity label information.
10
21
11
22
The core features of this proposal are as follows:
12
-
* Configure the allow list filter for Page Interaction Restriction Manager at the profile level.
13
-
* 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.
14
-
* When a label changes, an event is raised by WebView2 to hosted app with all the labels on that page.
23
+
* Configure the allow list filter for Page Interaction Restriction Manager at
24
+
the profile level.
25
+
* After the setup, the `Page Interaction Restriction Manager` is available on
26
+
pages in the allow list. Content can send sensitivity labels to the platform
27
+
via the API.
28
+
* When a label changes, an event is raised by WebView2 to hosted app with all
29
+
the labels on that page.
15
30
* Sensitivity labels are cleared when navigating away from the current WebView.
16
31
17
32
# Examples
18
33
19
34
## Setting up an allow list
20
35
21
-
Configure the PageInteractionRestrictionManager allow list to enable Sensitivity label functionality on trusted domains.
36
+
Configure the PageInteractionRestrictionManager allow list to enable Sensitivity
37
+
label functionality on trusted domains.
22
38
23
39
### C++ Sample
24
40
```cpp
@@ -28,8 +44,8 @@ void ConfigureAllowlist()
28
44
wil::com_ptr<ICoreWebView2Profile> profile;
29
45
CHECK_FAILURE(m_webView->get_Profile(&profile));
30
46
31
-
auto stagingProfile3 = profile.try_query<ICoreWebView2StagingProfile3>();
32
-
if (stagingProfile3) {
47
+
auto profile9 = profile.try_query<ICoreWebView2Profile9>();
0 commit comments