Closed Bug 1340849 Opened 9 years ago Closed 9 years ago

Jiminny

Categories

(Firefox Graveyard :: Screen Sharing Whitelist, defect)

All
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WONTFIX

People

(Reporter: james.graham, Unassigned)

Details

>> Vendor name Jiminny >> Point of contact james.graham@jiminny.com >> Site URLs https://app.staging.jiminny.com https://app.jiminny.com >> Does the application provide users with notice and control? ## Screensharing The screen sharing service enables organizer based screen sharing to other participants in your active web conference. Jiminny will never capture or share the contents of your screen without your prior consent. By starting a screen share session, you will be required to choose which portion(s) of your screen to share. Other participants are prompted to view your screen and may reject this. You may stop sharing your screen at any point. Jiminny does not store the contents of your screen on their servers. >> Have you seen and agree with the Developer Screen Sharing Submission policy? Yes >> Does the usage comply with the Developer Screen Sharing Submission Policy guidelines? Yes
Hi, I am resolving this bug as "won't fix", since starting Firefox 52 on April 18th the Screensharing whitelist is no longer needed to share your screen or windows. Please let us know if you find any problems! Much of this work was front-end, UX/UI changes, including support to let the UI know what streams are "scary" to share (see bug 1284910). See the meta bug 1127522 for all the work that went into this. Please read Jan-Ivar's blog post explaining the risks that users need to know about when sharing their screen or windows: https://blog.mozilla.org/webrtc/share-browser-windows-entire-screen-sites-trust/. The new UI permission dialog for screensharing links to a SUMO article with similar content to Jan-Ivar's post, but our SUMO team tailored it to a less technical user.
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → WONTFIX
Product: Firefox → Firefox Graveyard
You need to log in before you can comment on or make changes to this bug.