Enable tab sharing for Desktop targets and resolve any issues. UI changes will also be needed, and I believe changes to some MediaManager interfaces. We need to identify the right stable identifier for a tab so the UI can pass it to us.
Just so that this is recorded: As long as screensharing as a whole is guarded by the whitelist, this is OK, but I'd like us to develop the right UX before the whitelist comes off.
This likely needs to turn into a ux/ui bug because I believe the platform support for desktop is done modulo any testing bugs found.
backlog: --- → webRTC+
Priority: -- → P2
I ran into an issue with WebRTC in today's Nightly with tab sharing turned ON by default and no way to turn it off without killing the current call. It was alarming when the callee told me "Did you know I can see your browser tab?" Known issue?
(In reply to Jet Villegas (:jet) from comment #3) > I ran into an issue with WebRTC in today's Nightly with tab sharing turned > ON by default and no way to turn it off without killing the current call. It > was alarming when the callee told me "Did you know I can see your browser > tab?" Known issue? This is actually Hello, not in webrtc screen/etc sharing; they've been reworking it to be focused around tab-sharing. I think there's also a bug currently that you can't even 'pause' a tab-share in Hello.
ian, see comment 3
Mass change P2->P3 to align with new Mozilla triage process.
Priority: P2 → P3
You need to log in before you can comment on or make changes to this bug.