W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2019

[mediacapture-screen-share] Should the permissions UI be the first captured frame? (#108)

From: guest271314 via GitHub <sysbot+gh@w3.org>
Date: Wed, 29 May 2019 03:14:24 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issues.opened-449577356-1559099662-sysbot+gh@w3.org>
guest271314 has just created a new issue for https://github.com/w3c/mediacapture-screen-share:

== Should the permissions UI be the first captured frame? ==
Relevant specification sections

> [8. Security and Permissions](https://w3c.github.io/mediacapture-screen-share/#security-and-permissions)
> 
> Display capture that includes browser windows, particularly those that are under any form of control by the application, risks violation of these basic security protections. This risk is not entirely contained to browser windows, since control channels between browser applications and other applications, depending on the operating system. The key consideration is whether the captured display surface could be somehow induced to present information that would otherwise be secret from the application that is receiving the resulting media.
> 

> [8.1 Capturing Logical or Visible Display Surfaces](https://w3c.github.io/mediacapture-screen-share/#capturing-logical-or-visible-display-surfaces)
> Capture of logical display surfaces causes there to be a potential for content to be shared that a user is not made aware of. A logical display surface might render information that a user did not intend to expose. This can be more easily recognized if this information is visible. Such means are likely ineffectual against a machine, but a human recipient is less able to process content that appears only briefly.
> 
> Information that is not currently rendered to the screen SHOULD be obscured in captures unless the application has been specifically authorized to access that content (this might require elevated permissions).
> 
> How obscured areas of the logical display surface are captured to produce a visible display surface capture MAY vary. Some applications, like presentation software, benefit from having obscured portions of the screen render the image that appeared prior to being obscured. Freezing images can cause visual artifacts for changing content, or hide the fact that content is being obscured. Note that frozen portions of a capture can be incorrectly perceived as a bug. Alternatively, obscured areas might be replaced with content that marks them as being obscured, such as a grey color or hatching.
> 

Should the permissions UI where the user selects the screen, application or tab to be captured be the first captured frame if permission is granted to share the screen?

plnkr https://run.plnkr.co/preview/cjw8nj6cv00043n67mdqj2ae4/

![getDisplayImageFirstFrame1](https://user-images.githubusercontent.com/4174848/58526760-9df00400-81bf-11e9-9f19-802e400ca5f5.png)
![getDisplayImageFirstFrame2](https://user-images.githubusercontent.com/4174848/58526771-a6e0d580-81bf-11e9-8652-ca9ac060ac60.png)


Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/108 using your GitHub account
Received on Wednesday, 29 May 2019 03:14:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:22:23 UTC