Skip to content
This repository has been archived by the owner on Mar 14, 2024. It is now read-only.

Commit

Permalink
WIP
Browse files Browse the repository at this point in the history
  • Loading branch information
beaufortfrancois committed Sep 29, 2022
1 parent 20a446c commit 3d7a8c0
Show file tree
Hide file tree
Showing 3 changed files with 295 additions and 0 deletions.
1 change: 1 addition & 0 deletions site/_data/docs/web-platform/toc.yml
Original file line number Diff line number Diff line change
Expand Up @@ -4,6 +4,7 @@

- title: i18n.docs.web-platform.shipped
sections:
- url: /docs/web-platform/screen-sharing-controls
- url: /docs/web-platform/capture-handle
- url: /docs/web-platform/handwriting-recognition
- url: /docs/web-platform/navigation-api
Expand Down
100 changes: 100 additions & 0 deletions site/en/blog/avoiding-oversharing-when-screen-sharing/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,100 @@
---
layout: 'layouts/blog-post.njk'
title: 'Avoiding oversharing when screen sharing'
description: >
The web platform now ships with additional controls for privacy preserving screen sharing.
authors:
- beaufortfrancois
- eladalon
date: 2022-09-28
hero: image/vvhSqZboQoZZN9wBvoXq72wzGAf1/fr1l39yWeyjH8uAZlIbC.jpeg
alt: three person pointing the silver laptop computer photo
tags:
- chrome-105
- chrome-107
---

Sharing tabs, windows, and screens is already possible on the web platform thanks to [`getDisplayMedia()`]. We’re now shipping the following improvements that guide the user away from accidental oversharing:

- Sharing tabs is now the default option, rather than sharing screens.
- The `displaySurface` option can indicate that the web app prefers to offer a specific display surface type (tabs, windows, or screens).
- The `surfaceSwitching` option indicates whether Chrome should allow the user to dynamically switch between shared tabs.
- The `selfBrowserSurface` option can be used to prevent the user from sharing the current tab. This avoids the "hall of mirrors" effect.
- The `systemAudio` option ensures Chrome only offers relevant audio-capture to the user.

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/SRzjjJ9AQVQVyjTCXskh.png", alt="Screenshot of the media picker prompt upon calling getDisplayMedia().", width="800", height="524" %}
<figcaption>
Chrome’s media picker prompt upon calling getDisplayMedia().
</figcaption>
</figure>

## Reordering the selection offered to the user {: #reordering }

When [`getDisplayMedia()`] is called, users are presented with a media picker which allows them to share whichever display surface they would like any tab, window, or screen. Experience shows that the ordering of the offering affects the users’ selection. We are experimenting in Chrome&nbsp;107 on desktop with reordering the picker in order to nudge users towards tabs, which is the best option in the majority of cases.

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/7z4i2ZI77UZA80WRg4Rc.jpg", alt="Screenshots of the old and new media picker prompts.", width="800", height="556" %}
<figcaption>
Chrome’s media picker (old vs. new).
</figcaption>
</figure>

The expected benefits are as follows:

### Privacy

Previously, screens were offered as the most prominent option. This is the least privacy-preserving option, as users may end up exposing more personal information than they had originally intended. Such as:
- Timezone (via the system clock)
- Language
- System notifications
- Running apps
- Installed apps
- Installed extensions
- Bookmarks
- Browsing history (via the omnibox)
- The user’s profile pictures (browser, system, other apps)
- Rugby-club affiliation (via desktop wallpapers)
- Audio notifications from backgrounded apps, like a calendar

Most of these concerns are mitigated by sharing a tab instead of a screen.

### Feature-completeness

Tab sharing is more feature-complete:
- Sharing tab audio is supported on all platforms; sharing system audio and window audio is only implemented on some platforms, at the time of writing.
- When sharing tabs, complementary features enable closer collaboration with the captured content:
- [Capture Handle] allows the identification of the captured tab and establishment of a communications channel with it.
- [Region Capture] allows further scoping down of captured content.

### Performance and User Experience

When a user intends to share another web app, it’s preferable to directly share the tab running that app, rather than its Chrome window, or even the entire screen.
- The tab will continue being shared even if the user interacts with another app.
- The resulting image on remote users’ participants is going to be “zoomed in on the action” and therefore clearer.
- Avoiding the capture, encoding and transmission of irrelevant content saves CPU and bandwidth.
- A more stable frame-rate is possible for tab-capture than for other types of capture.

## New screen sharing controls

The new `displaySurface`, `surfaceSwitching`, `selfBrowserSurface`, and `systemAudio` options will allow you to tailor your screen sharing experience.

Check out [Privacy-preserving screen sharing controls] for more information.

## What's next {: #future }

[Conditional Focus] will allow the capturing web app to instruct the browser to either switch focus to the captured display surface, or to avoid such a focus change.

## Acknowledgements

Hero image by [Jelleke Vanooteghem].

Thanks to [Rachel Andrew] for reviewing this article.

[`getdisplaymedia()`]: https://developer.mozilla.org/docs/Web/API/MediaDevices/getDisplayMedia
[capture handle]: /docs/web-platform/capture-handle/
[region capture]: /docs/web-platform/region-capture/
[privacy-preserving screen sharing controls]: /docs/web-platform/screen-sharing-controls/
[conditional focus]: https://wicg.github.io/conditional-focus/
[jelleke vanooteghem]: https://unsplash.com/photos/kabtmcdcAbk
[rachel andrew]: https://github.com/rachelandrew
194 changes: 194 additions & 0 deletions site/en/docs/web-platform/screen-sharing-controls/index.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,194 @@
---
layout: 'layouts/doc-post.njk'
title: 'Privacy-preserving screen sharing controls'
description: >
Guide the user away from oversharing thanks to privacy-preserving screen sharing controls on the web.
authors:
- beaufortfrancois
- eladalon
date: 2022-09-28
hero: image/vvhSqZboQoZZN9wBvoXq72wzGAf1/5VpvNzrvEM3qSxasqP1j.jpeg
alt: toddler holding her lips photo
tags:
- chrome-105
- chrome-107
---

The [Screen Capture API] introduces additions to the existing Media Capture and Streams API to let the user select a screen or portion of a screen (such as a window) to capture as a media stream. This stream can then be recorded or shared with others over the network. This documentation introduces some changes to the API to better preserve privacy, and prevent accidental sharing of personal information.

Here’s a list of controls you can use for privacy preserving screen sharing:
- The `displaySurface` option can indicate that the web app prefers to offer a specific display surface type (tabs, windows, or screens).
- The `surfaceSwitching` option indicates whether Chrome should allow the user to dynamically switch between shared tabs.
- The `selfBrowserSurface` option can be used to prevent the user from sharing the current tab. This avoids the "hall of mirrors" effect.
- The `systemAudio` option ensures Chrome only offers relevant audio-capture to the user.

## Changes to `getDisplayMedia()`

The following changes have been made to [`getDisplayMedia()`].

### The `displaySurface` option {: #displaySurface }

Web apps with specialized user journeys, which work best with sharing a window or a screen, can still ask Chrome to offer windows or screens more prominently in the media picker. The ordering of the offer remains unchanged, but the relevant pane is pre-selected.

The values for the [`displaySurface`] option are:
- `"browser"` for tabs.
- `"window"` for windows.
- `"monitor"` for screens.

```js
const stream = await navigator.mediaDevices.getDisplayMedia({
video: true,
displaySurface: "window", // Pre-select the "Window" pane in the media picker.
});
```

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/AaQIUrKKCvoNuaBjvGOM.png", alt="Screenshot of the media picker featuring the pre-selected \"Window\" pane.", width="800", height="524" %}
<figcaption>
The "Window" pane is pre-selected in the media picker.
</figcaption>
</figure>

Note that we don’t offer the option to pre-select a specific window or screen. This is by design, as that would give the web app too much power over the user.

### The `surfaceSwitching` option {: #surfaceSwitching }

One of the top-cited reasons for sharing the entire screen, is the desire to seamlessly switch between sharing different surfaces during a session. To address this, Chrome now exposes a button that lets a user dynamically switch between sharing different tabs. This "Share this tab instead" button has previously been available to Chrome extensions, and can now be used by any web app which calls [`getDisplayMedia()`].

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/NdHrtlD1vZAcrcnLSprF.png", alt="Screenshot of the button used to dynamically switch between sharing different tabs", width="800", height="524" %}
<figcaption>
The "Share this tab instead" button in Chrome.
</figcaption>
</figure>

If [`surfaceSwitching`] is set to `"include"`, the browser will expose said button. If set to `"exclude"`, it will refrain from showing the user that button. Web apps are encouraged to set an explicit value, since Chrome might change the default value over time.

```js
const stream = await navigator.mediaDevices.getDisplayMedia({
video: true,
// Ask Chrome to expose browser-level UX elements that allow
// the user to switch the underlying track at any time,
// initiated by the user and without prior action by the web app.
surfaceSwitching: "include"
});
```

### The `selfBrowserSurface` option {: #selfBrowserSurface }

By default, [`getDisplayMedia()`] offers sharing any tab. In video conferencing scenarios, users often make the mistake of selecting the video conferencing tab itself, leading to a "hall of mirrors" effect, howling and general confusion.

To protect users from themselves, video conferencing web apps can now set [`selfBrowserSurface`] to `"exclude"`. Chrome will then exclude the current tab from the list of tabs offered to the user.

```js
const stream = await navigator.mediaDevices.getDisplayMedia({
video: true,
selfBrowserSurface: "exclude" // Avoid 🦶🔫.
});
```

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/CtF2KFIwXjCantVBhmMR.png", alt="Screenshot of the media picker excluding the current tab", width="800", height="524" %}
<figcaption>
The current tab is excluded, only the second tab is present.
</figcaption>
</figure>

Presently, the default value for `selfBrowserSurface` is `"include"`, but web apps are encouraged to set it explicitly, as the default may change in the future.

Note that `selfBrowserSurface: "exclude"` is mutually exclusive with [`preferCurrentTab: true`].

### The `systemAudio` option {: #systemAudio }

[`getDisplayMedia()`] allows capturing audio alongside video. But not all audio is created equal. Consider video conferencing web apps:
- If the user shares another tab, it makes sense to capture audio as well.
- System audio, on the other hand, includes remote participants' own audio, and should not be transmitted back to them.

In the future, it may be possible to exclude some audio sources from the capture. But for now, video conferencing web apps often find it best to just avoid capturing system audio. This could previously be done by checking what display surface the user chose, and stopping the audio track if they chose to share a screen. However, this raises a small issue, in that some users are confused when they explicitly check the checkbox to share system audio, and are then told by remote participants that no audio is incoming.

<figure>
{% Img src="image/vvhSqZboQoZZN9wBvoXq72wzGAf1/G6ipYLLSEMTutcu1wtJJ.jpg", alt="Screenshots of media pickers featuring tab audio sharing", width="800", height="556" %}
<figcaption>
Sharing tab audio is offered in "Chrome Tab" pane, but not in "Entire Screen" pane.
</figcaption>
</figure>

By setting [`systemAudio`] to `"exclude"`, a web app can avoid baffling users through mixed signals. Chrome will offer to capture audio alongside tabs and windows, but not alongside screens.

```js
const stream = await navigator.mediaDevices.getDisplayMedia({
video: true,
audio: true, // Ask to capture audio; caveat follows.
systemAudio: "exclude" // Do not offer to capture *system* audio.
});
```

Presently, the default value for `systemAudio` is `"include"`, but web apps are encouraged to set it explicitly, as the default may change in the future.

## Demo {: #demo }

You can play with these screen sharing controls by running the [demo] on Glitch. Be sure to [check out the source code].

{% Glitch { id: 'screen-sharing-controls', path: 'index.js', previewSize: 0 } %}

## Browser support {: #browser-support }

`displaySurface`, `surfaceSwitching`, and `selfBrowserSurface` are available in Chrome&nbsp;107 on desktop. `systemAudio` is available in Chrome&nbsp;105 on desktop.

## Feedback {: #feedback }

The Chrome team and the web standards community want to hear about your experiences with those screen sharing controls.

### Tell us about the design

Is there something about those screen sharing controls that doesn't work as you expected? Or are there missing methods or properties that you need to implement your idea? Have a question or comment on the security model?

* File a spec issue on the [GitHub repo][issues], or add your thoughts to an existing issue.

### Problem with the implementation?

Did you find a bug with Chrome's implementation? Or is the implementation different from the spec?

* File a bug at <https://new.crbug.com>. Be sure to include as much detail as you can, and simple instructions for reproducing. [Glitch](https://glitch.com) works well for sharing code.

### Show support

Are you planning to use those screen sharing controls? Your public support helps the Chrome team prioritize features and shows other browser vendors how critical it is to support them.

Send a tweet to [@ChromiumDev] and let us know where and how you are using it.

## Helpful links {: #links }

- [Specification][spec]
- [`displaySurface` explainer]
- [`surfaceSwitching` explainer]
- [`selfBrowserSurface` explainer]
- [`systemAudio` explainer]
- [TAG review][tag]

## Acknowledgements

Hero image by [John Schnobrich].

Thanks to [Rachel Andrew] for reviewing this article.

[screen capture api]: https://w3c.github.io/mediacapture-screen-share/
[`getdisplaymedia()`]: https://developer.mozilla.org/docs/web/api/mediadevices/getdisplaymedia
[`displaysurface`]: https://w3c.github.io/mediacapture-screen-share/#dfn-displaysurface
[`surfaceswitching`]: https://w3c.github.io/mediacapture-screen-share/#dom-displaymediastreamoptions-surfaceswitching
[`selfbrowsersurface`]: https://w3c.github.io/mediacapture-screen-share/#dom-displaymediastreamoptions-selfbrowsersurface
[`prefercurrenttab: true`]: https://wicg.github.io/prefer-current-tab/
[`systemaudio`]: https://w3c.github.io/mediacapture-screen-share/#dom-displaymediastreamoptions-systemaudio
[demo]: https://screen-sharing-controls.glitch.me/
[check out the source code]: https://glitch.com/edit/#!/screen-sharing-controls?path=index.js
[conditional focus]: https://wicg.github.io/conditional-focus/
[issues]: https://github.com/w3c/mediacapture-screen-share/issues/
[@chromiumdev]: https://twitter.com/chromiumdev
[spec]: https://w3c.github.io/mediacapture-screen-share/
[`displaysurface` explainer]: https://github.com/eladalon1983/screen-share-explainers/blob/main/displaysurface_constraint_explainer.md
[`surfaceswitching` explainer]: https://github.com/eladalon1983/screen-share-explainers/blob/main/surfaceswitching_explainer.md
[`selfbrowsersurface` explainer]: https://github.com/eladalon1983/screen-share-explainers/blob/main/selfbrowsersurface_explainer.md
[`systemaudio` explainer]: https://github.com/eladalon1983/screen-share-explainers/blob/main/systemaudio_explainer.md
[tag]: https://github.com/w3ctag/design-reviews/issues/744
[john schnobrich]: https://unsplash.com/photos/2FPjlAyMQTA
[rachel andrew]: https://github.com/rachelandrew

0 comments on commit 3d7a8c0

Please sign in to comment.