Changes

Jump to: navigation, search

Screensharing

1,869 bytes removed, 16:47, 22 February 2017
updated for 52
To try it, goto [https://mozilla.github.io/webrtc-landing/gum_test.html getUserMedia tests].
==Project Status UpdatesNoteworthy Changes: ==*Firefox 33**'''IMPORTANT:''' The Screensharing on all Desktop platforms, except Mac 10.6 and WinXP***Those platforms need whitelist is no longer needed to set a pref for Screensharing. It was disabled by default because it was crashing automated testsshare your screen or windows starting Firefox 52 (April). If there's enough interest, we may attempt to get them working later, and of course contributors are welcome to work on getting 10.6 and WinXP enabled by default - contact Please let us on IRC in #media know if interested.you find any problems!***To safeguard the security Much of our usersthis work was front-end, by default Mozilla blocks unknown websitesUX/apps from using Screensharing. We UI changes, including support to let the UI know what streams are testing designs for interface options "scary" to enable users to make an informed choice on whether to allow screensharing with a particular site, but there is the existing challenge of doing this in a way that both clearly informs users of the risks and doesn’t create an overly-burdensome user experience. share (see policy below{{bug|1284910}})*FxOS screen sharing** Screen sharing will come to FxOS in a future release ==Developer Screensharing Submission Policy==We look for the following things when deciding whether a screensharing application is appropriate for inclusion on our screensharing whitelist: Screensharing applications must provide users with notice and control. For example:  *Describe to users clearly and accessibly how See the screensharing application handles and shares information in connection with the screenshare stream (meta {{bug|1127522}} for example, in a privacy policy or all the UI)*Transmit only the specific content work that the user directs to be transmitted (“'''User Directed Content'''”)*Transmit User Directed Content only to the user’s intended recipients  Screensharing applications must not harm users or Mozillawent into this. For example: *Don’t use the whitelist to engage in illegal activity*Don’t engage in activity that is deceptive, misleading, fraudulent, designed to lead to identity theft, or designed to maliciously intercept and monitor communications and content*Don’t engage in activity designed to share, modify or capture content not intended to be shared by Please read Jan-Ivar's blog post explaining the user*Don’t engage in any activity risks that interferes with or disrupts Mozilla’s services or products (or the servers and networks which are connected users need to Mozilla’s services) This list is illustrative, not definitive, and may be updated.  Mozilla reserves the right to remove from our whitelist any screensharing application that it deems in violation of this policy. ==Filing a bugzilla request for addition to the know about when sharing their screen sharing whitelist== A bugzilla template to request addition to the whitelist will be available shortly. If you have a request now, please file a New bug using this template or windows: https://bugzillablog.mozilla.org/form.webrtc/share-browser-windows-entire-screen-sites-trust/.share ** The new UI permission dialog for screensharing links to a SUMO article which is currently identical to Jan-Ivar's post, but our SUMO team will be tailoring it to a less technical user before Fx 52 goes to Beta.whitelist
Confirm
1,094
edits

Navigation menu