Skip to content

Commit 2937741

Browse files
Update Background and Description
1 parent 9e668d1 commit 2937741

1 file changed

Lines changed: 6 additions & 6 deletions

File tree

specs/SensitivityLabel.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -2,16 +2,16 @@ Sensitivity label support for Webview2
22
===
33

44
# 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 (see details here), 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 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.
66

77
# Description
88

9-
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 URLs 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 URLs. By default, the allow list is empty, preventing hosted content from transmitting sensitivity label information.
9+
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.
1010
The core features of this proposal are as follows:
11-
Configure the allowlist filter for Page Interaction Restriction Manager at the profile level.
12-
After setup, the manager is available on allowlisted pages. Content can send sensitivity labels to the platform via the API.
13-
When a label changes, an event notifies the platform of all labels on that page.
14-
Sensitivity labels are cleared when navigating away from the current WebView.
11+
* Configure the allowlist filter for Page Interaction Restriction Manager at the profile level.
12+
* After setup, the manager is available on allowlisted pages. Content can send sensitivity labels to the platform via the API.
13+
* When a label changes, an event notifies the platform of all labels on that page.
14+
* Sensitivity labels are cleared when navigating away from the current WebView.
1515

1616
# Examples
1717

0 commit comments

Comments
 (0)