Skip to content

Commit cbcf415

Browse files
Address PR comments iteration 1
1 parent 1135b81 commit cbcf415

1 file changed

Lines changed: 10 additions & 12 deletions

File tree

specs/SensitivityLabel.md

Lines changed: 10 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -2,28 +2,26 @@ 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](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.
66

77
## 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.
119

1210
# Description
1311

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.
1513

1614
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.
1917
* When a label changes, an event is raised by WebView2 to hosted app with all the labels on that page.
2018
* Sensitivity labels are cleared when navigating away from the current WebView.
2119

2220
# Examples
2321

24-
## Setting Up an Allowlist
22+
## Setting up an allow list
2523

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.
2725

2826
```cpp
2927
void ConfigureAllowlist()
@@ -34,7 +32,7 @@ void ConfigureAllowlist()
3432

3533
auto stagingProfile3 = profile.try_query<ICoreWebView2StagingProfile3>();
3634
if (stagingProfile3) {
37-
// Create allowlist with trusted URLs
35+
// Create allow list with trusted URLs
3836
std::vector<std::wstring> allowlist = {
3937
L"https://intranet.company.com/*",
4038
L"https://*.company.com/*",
@@ -59,15 +57,15 @@ void ConfigureAllowlist()
5957
items.data(),
6058
&stringCollection));
6159

62-
// Apply the allowlist
60+
// Apply the allow list
6361
CHECK_FAILURE(stagingProfile3->put_PageInteractionRestrictionManagerAllowlist(
6462
stringCollection.get()));
6563
}
6664
}
6765
}
6866
```
6967

70-
## Retrieving Current Allowlist
68+
## Retrieving current allow list
7169

7270
```cpp
7371
void GetCurrentAllowlist()

0 commit comments

Comments
 (0)