Closed
Bug 1509472
(socket-proc-webrtc)
Opened 7 years ago
Closed 1 year ago
[meta] Socket Process Isolation work for only WebRTC support
Categories
(Core :: Networking, enhancement, P3)
Core
Networking
Tracking
()
RESOLVED
FIXED
| Tracking | Status | |
|---|---|---|
| firefox65 | --- | affected |
People
(Reporter: mayhemer, Unassigned)
References
(Blocks 2 open bugs)
Details
(Keywords: meta, Whiteboard: [necko-triaged])
This is about to track the necessary subset of SPI stuff we have to deliver to support WebRTC networking on an isolated process.
This is a P1, since the WebRTC team wants to deliver till the end of 2018.
|
Reporter | |
Updated•7 years ago
|
Alias: socket-proc-webrtc
|
|
Reporter | |
Updated•7 years ago
|
|
|
Reporter | |
Updated•7 years ago
|
Blocks: webrtc-sock-proc
|
||
Updated•7 years ago
|
Whiteboard: [necko-triaged]
|
|
Reporter | |
Comment 2•7 years ago
|
||
Dragana, it looks like you took over this project, or at least you are giving it more time than I do, lately. Are you OK if I reassign this to you? Feel free to bounce if you are overly busy and can't take care of this one. Thanks.
Assignee: honzab.moz → dd.mozilla
|
||
Comment 3•5 years ago
|
||
Nils said this doesn't block anything for Fission.
No longer blocks: fission
|
||
Updated•4 years ago
|
Assignee: dd.mozilla → nobody
Priority: P1 → P3
|
||
Updated•3 years ago
|
Severity: normal → S3
|
||
Comment 4•1 year ago
|
||
We already shipped socket process, so I think we can close this bug.
Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•