Closed
Bug 1284201
Opened 8 years ago
Closed 8 years ago
Shared workers should support multiple content processes
Categories
(Core :: DOM: Workers, defect)
Core
DOM: Workers
Tracking
()
RESOLVED
DUPLICATE
of bug 1207778
| Tracking | Status | |
|---|---|---|
| e10s | - | --- |
People
(Reporter: gkrizsanits, Unassigned)
References
Details
(Whiteboard: [e10s-multi:M3])
Currently if two tabs from two separate content processes with same origin create a shared worker, they create separate instances instead of using a shared one.
|
Reporter | |
Updated•8 years ago
|
Blocks: e10s-multi
Whiteboard: [e10s-multi:M1]
tracking-e10s:
--- → ?
|
|
Reporter | |
Comment 1•8 years ago
|
||
This is an e10s-multi only issue. With single content process e10s this problem can never happen.
|
||
Updated•8 years ago
|
|
||
Updated•8 years ago
|
Whiteboard: [e10s-multi:M1] → [e10s-multi:M3]
|
|
Reporter | |
Updated•8 years ago
|
Blocks: e10s-multi-beta
|
|
||
Updated•8 years ago
|
|
||
Comment 4•8 years ago
|
||
Initially bug 1207778 was just for ServiceWorker. Now it's about SharedWorkers. I mark this bug as duplicate of bug 1207778.
Status: NEW → RESOLVED
Closed: 8 years ago
Flags: needinfo?(amarchesini)
Resolution: --- → DUPLICATE
|
|
Reporter | |
Updated•8 years ago
|
Flags: needinfo?(gkrizsanits)
You need to log in
before you can comment on or make changes to this bug.
Description
•