Open
Bug 1991617
Opened 1 year ago
Updated 6 days ago
Implement MediaStreamTrackProcessor behind a pref
Categories
(Core :: WebRTC: Audio/Video, task, P3)
Core
WebRTC: Audio/Video
Tracking
()
NEW
People
(Reporter: pehrsons, Assigned: az)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: parity-chrome, parity-safari)
Attachments
(1 file)
No description provided.
| Reporter | ||
Updated•1 year ago
|
Priority: P2 → P3
Updated•3 months ago
|
Keywords: parity-chrome,
parity-safari
| Reporter | ||
Comment 1•20 days ago
|
||
A worker has no consumer that can render a MediaStreamTrack without
exposing its data to script, so data under a principal the worker cannot
access must never reach it. Per mediacapture-fromelement's security
considerations this includes media that switches to a cross-origin source
while captured. The test captures a same-origin, a cross-origin and a
CORS-loaded video with mozCaptureStream(), transfers the track to a worker
and reads frames with MediaStreamTrackProcessor, expecting real frames only
for the same-origin and CORS cases.
MediaStreamTrackProcessor is not implemented, so the expectations are FAIL
until it is. Implementing it, or any other worker consumer of track data,
must flip them.
You need to log in
before you can comment on or make changes to this bug.
Description
•