Open
Bug 1475360
Opened 6 years ago
Updated 2 years ago
Implement MediaStreamTrack isolated/onisolationchange
Categories
(Core :: WebRTC, enhancement, P3)
Core
WebRTC
Tracking
()
NEW
People
(Reporter: sheppy, Unassigned)
References
()
Details
Attachments
(8 files)
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review | |
47 bytes,
text/x-phabricator-request
|
Details | Review |
The WebRTC spec, section 10.4.1 (https://w3c.github.io/webrtc-pc/#isolated-track), specifies additions to the MediaStreamTrack interface: the isolated attribute and the onisolationchange event handler (for the event isolationchange). isolated is true if the MediaStreamTrack is isolated by either its peerIdentity being set or because the track's contents come from a cross-origin source.
This should be implemented in order to simplify detection of isolation and changes to the isolation state of a track.
Updated•6 years ago
|
Component: Audio/Video → WebRTC
Priority: -- → P3
Comment 1•6 years ago
|
||
Is there a specification compliant procedure to set the peerIdentity?
Comment 2•5 years ago
|
||
I don't think this will be too hard to implement generically in MediaStreamTrack.
Assignee: nobody → apehrson
Updated•5 years ago
|
Status: NEW → ASSIGNED
Comment 3•5 years ago
|
||
With bug 1212237 fixed so that the SecurityError reported there does not happen frequently, I no longer have justification for implementing this. It could still be done, should we want to invest more in shipping all parts of webrtc-identity. I'll upload the patches I have in their current state for the record.
Comment 4•5 years ago
|
||
Comment 5•5 years ago
|
||
Depends on D48681
Comment 6•5 years ago
|
||
Depends on D48682
Comment 7•5 years ago
|
||
Depends on D48683
Comment 8•5 years ago
|
||
Depends on D48684
Comment 9•5 years ago
|
||
Depends on D48685
Comment 10•5 years ago
|
||
Depends on D48686
Comment 11•5 years ago
|
||
Depends on D48687
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•