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

RE: Gutting the screen sharing constraints

From: Keith Griffin (kegriffi) <kegriffi@cisco.com>
Date: Thu, 29 Oct 2015 11:35:02 +0000
To: Martin Thomson <martin.thomson@gmail.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <77093fd7b8074bcabebd4b87d1faa43c@XCH-ALN-010.cisco.com>
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 {

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 11:35:57 UTC

This archive was generated by hypermail 2.3.1 : Thursday, 29 October 2015 11:35:58 UTC