W3C home > Mailing lists > Public > public-webrtc@w3.org > November 2013

Re: Why does screen sharing require a browser extension?

From: cowwoc <cowwoc@bbs.darktech.org>
Date: Wed, 27 Nov 2013 13:11:31 -0500
Message-ID: <529635D3.3000309@bbs.darktech.org>
To: Justin Uberti <juberti@google.com>, Lorenzo Miniero <lorenzo@meetecho.com>
CC: Silvia Pfeiffer <silviapfeiffer1@gmail.com>, Martin Thomson <martin.thomson@gmail.com>, "public-webrtc@w3.org" <public-webrtc@w3.org>
On 27/11/2013 12:10 PM, Justin Uberti wrote:
> The publisher of the extension can control which domains can talk to 
> it. See 
> http://developer.chrome.com/extensions/manifest/externally_connectable.html. 
> This would allow you to make your extension available to 
> yourcompany.com <http://yourcompany.com>, as well as development 
> machines on *.corp.yourcompany.com <http://corp.yourcompany.com>. 
> (Note that *.com and other wide-reaching wildcards are not permitted.)
> There is also the Chrome flag parameter to force on the screen-sharing 
> feature for testing purposes 
> (chrome://flags/#enable-usermedia-screen-capture).

So you're saying we will never be able to implement "help your mom with 
her computer" style applications in WebRTC? Those kind of apps have no 
way of knowing ahead of time which websites they will navigate to.

Received on Wednesday, 27 November 2013 18:12:50 UTC

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