Closed Bug 1035577 Opened 6 years ago Closed 6 years ago
Breakdown -- Screen sharing permissions UI for Web
RTC web apps
+++ This bug was initially created as a clone of Bug #1031424 +++
Assignee: nobody → florian
Status: NEW → ASSIGNED
Iteration: --- → 33.3
Points: --- → 3
We agreed in bug 1031424 on the UI we want to implement for Firefox 33, see attachment 8453837 [details] for the final UI. Here is a break down of the work needed to make it happen: Bug 1037424 - implement a whitelist of web sites allowed to use screensharing in Firefox 33 This bug could either be handled in the UI or in the back-end, and so could either be addressed by the Firefox or WebRTC team. Bug 1037405 - implement the screen/app sharing doorhangers I'm taking this. Bug 1037408 - implement the global getUserMedia indicator Gijs is taking this. Bug 1037415 - remove existing webrtc indicator in the browser toolbar Bug 1037418 - [UX] provide new icons for screensharing UI Philipp told me a single bug for the icons is fine, but if needed we could further break it down in these 3 parts: -- screensharing urlbar icon -- screensharing doorhanger icon -- global indicator icons Not strictly required for Firefox 33 but good to have: Bug 1037430 - implement webrtc global indicator in the Mac menubar [platform] Bug 1037433 - add platform support for menubar icons Bug 1037438 - implement 'Never Share' persistent permissions for screen sharing
That looks like a good breakdown. (In reply to Florian Quèze [:florian] [:flo] from comment #1) > Bug 1037424 - implement a whitelist of web sites allowed to use > screensharing in Firefox 33 > This bug could either be handled in the UI or in the back-end, and so could > either be addressed by the Firefox or WebRTC team. I think that this is best handled in the DOM. That way we can be more responsive to requests for screensharing. Once we open this up to more than just the whitelist and only use the whitelist for firefox/tabs and desktop sharing, then that code will need to live in the DOM anyway.
You need to log in before you can comment on or make changes to this bug.