W3C home > Mailing lists > Public > public-media-capture@w3.org > October 2015

Re: Gutting the screen sharing constraints

From: Martin Thomson <martin.thomson@gmail.com>
Date: Thu, 29 Oct 2015 23:12:49 +0900
Message-ID: <CABkgnnVDy7w99pw4ES3_6r89EPAAQUUPfot96sy+PTAekY3qHA@mail.gmail.com>
To: "Keith Griffin (kegriffi)" <kegriffi@cisco.com>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
No, the idea here is to remove all the screen-sharing constraints.
You would have a single call that caused the user to select what to
share.  This would bundle all those various types of thing into the
same prompt always.  The browser might probably want to structure the
question somehow to aid comprehension.

This would prevent a site from directly requesting "monitor" or
"browser" sharing (i.e., the least safe options).  We might still
retain those terms in the document, but they would not be API-visible
constructs.

On 29 October 2015 at 20:35, Keith Griffin (kegriffi)
<kegriffi@cisco.com> wrote:
> Just to be clear, in your proposed change we would keep the enum for each capture type so that the sharing application can present different share options to the user and to capture user consent.
>
> enum OutputCaptureSurfaceType {
>     "monitor",
>     "window",
>     "application",
>     "browser"
> };
>
> Authorising the display capture would not require application constraints to be pushed to the user. The user would choose what they want to share from the list of defined capture types?
>
>
> -----Original Message-----
> From: Martin Thomson [mailto:martin.thomson@gmail.com]
> Sent: 29 October 2015 07:55
> To: public-media-capture@w3.org
> Subject: Gutting the screen sharing constraints
>
> At the last meeting, we more or less agreed to remove the distinction between "application" sharing and "window" sharing.
>
> After a lot more thought about this, I want to suggest a more dramatic
> change: removing the constraints that allow an application to restrict which display surfaces are offered to the user to select from.
>
> I originally added these constraints because that is how the Firefox implementation works.  But the more that I think about this, the less sense it makes in the general case.  Having the application push particular options to the fore is fraught from a security perspective and it's not clear that narrowing the selection has been of much use in applications.  Letting the user choose seems like the best option.
>
> If we think that narrowing the selection is necessary for UX reasons, I think that we can easily find better UX options.
>
Received on Thursday, 29 October 2015 14:13:21 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 14:13:22 UTC