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

RESOLVED INVALID

Status

Hello (Loop)
Client
P1
normal
RESOLVED INVALID
3 years ago
3 years ago

People

(Reporter: mikedeboer, Assigned: mikedeboer)

Tracking

unspecified
Points:
3
Dependency tree / graph
Bug Flags:
firefox-backlog +
qe-verify -

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Assignee)

Description

3 years ago
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.
Flags: qe-verify-
(Assignee)

Updated

3 years ago
Blocks: 1131574
(Assignee)

Comment 1

3 years ago
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.
Depends on: 1131587

Comment 3

3 years ago
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.
backlog: --- → Fx38+
Target Milestone: mozilla38 → ---
(Assignee)

Updated

3 years ago
Assignee: nobody → mdeboer
Status: NEW → ASSIGNED
Iteration: --- → 38.3 - 23 Feb
Flags: firefox-backlog+
(Assignee)

Comment 4

3 years ago
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.
Status: ASSIGNED → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.