1131570 - Implement tab-source-service provider that shares the active tab

Status: RESOLVED INVALID

(Hello (Loop) :: Client, defect, P1)

Description

[Mike de Boer [:mikedeboer]]

This is a first step to supporting a 'browser' video source, aka tab sharing.
Once the gUM request for a browser window comes is, the tab-source-service - implemented in JS - will offer the content window of the currently selected tab to start streaming.

See the URL for an example from :dmose.

Comment 1

[Mike de Boer [:mikedeboer]]

It's important to note that ONLY requests from the page about:loopconversation are allowed to stream tabs at this point. See bug 1131587 for an additional place to enforce this restriction.

Comment 2

[Mike de Boer [:mikedeboer]]

Another reference implementation from Fennec: https://dxr.mozilla.org/mozilla-central/source/mobile/android/components/TabSource.js

Comment 3

[:shell escalante]

triaging to blocking-loop:Fx38+ for tracking this release, all bugs in 38+ and 38? now, will move to "backlog+" for Fx39.  After that - we won't triage to a specific release any longer.  we will work from an ordered backlog.

Comment 4

[Mike de Boer [:mikedeboer]]

As per bug 1131568 comment 3, this approach is invalid.

We'll need to supply the window ID of the contentWindow of the currently active tab to gUM (read: SDK). This is according to the most recent browser sharing implementation.

:blassey also mentioned that the tab-source-service mechanism is deprecated in favor of the aforementioned approach and will be removed from the tree as soon as the Android implementation is updated.

Instead, we'll implement bug 1133493.