Closed Bug 906956 Opened 11 years ago Closed 9 years ago

Screen sharing UI design and implementation

Categories

(Core :: WebRTC, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: jesup, Unassigned)

References

Details

(Whiteboard: [webrtc][meta])

This is to track the UI and UX for screen sharing.

Note that for the general case (as opposed to the simple Chromecast type of case) there are significant security and privacy issues.  Any design will need to take these into account.  This should also be coordinated with the W3.

Google has a tab-sharing implementation, but it's behind a flag due to security issues among other things.
Flags: sec-review?
(In reply to Randell Jesup [:jesup] from comment #0)
> Google has a tab-sharing implementation, but it's behind a flag due to
> security issues among other things.

Is this bug about "tab" sharing, or true "screen" sharing like other video conferencing software?
We think this needs an architecture (team style review)[:curtis], a code review[:dveditz] and a technical privacy review[:curtisk].
(In reply to Daniel Veditz [:dveditz] from comment #1)
> (In reply to Randell Jesup [:jesup] from comment #0)
> > Google has a tab-sharing implementation, but it's behind a flag due to
> > security issues among other things.
> 
> Is this bug about "tab" sharing, or true "screen" sharing like other video
> conferencing software?

Both are desired, and the solutions for them should be related (though not identical).  The main interests from people will be tab sharing, window sharing (including non-browser windows), and full-screen sharing.  We have external people willing to contribute to designing and implementing this.

Note that right now Google is using site-specific extensions to enable the site to share screens (i.e. push the approval off to the extension-install).
I don't see the bugs mentioned in comment 2. Since it's Friday afternoon I'll put sec-review? back so we don't forget it over the weekend.

(In reply to Randell Jesup [:jesup] from comment #3)
> Both are desired, and the solutions for them should be related (though not
> identical).  The main interests from people will be tab sharing, window
> sharing (including non-browser windows), and full-screen sharing.

I asked because screen sharing would presumably require more platform-specific code than tab sharing and might take more work to review. It also raises some additional privacy issues (more about notification/UI that the user knows it's going to happen than whether or not to do it, since obviously in many situations that /is/ what users want).
Flags: sec-review?
bugs filled, flag removed
Flags: sec-review?
See also bug 923228.  There's an add-on linked to from there which is just starting to be usable for prototyping various user experiences on desktop.
All the dependencies for this are resolved and screensharing has shipped.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Whiteboard: [webrtc] → [webrtc][meta]
You need to log in before you can comment on or make changes to this bug.