667501 - Implement .postMessage for multiple content processes

Status: RESOLVED DUPLICATE of bug 1204775

(Core :: DOM: Core & HTML, defect)

Description

[Benjamin Smedberg]

.postMessage will need a broadcast mechanic to work across multiple content processes

Comment 2

[Boris Zbarsky [:bzbarsky]]

postMessage targets a particular window, no?  And it's a window you have a reference to.  So it's generally in the same process as you already (modulo the bit about setting openers to null), or am I misunderstanding the setup?

Comment 3

[Olli Pettay [:smaug][[e-mail]]]

This is about window.postMessage and not sharedWorker.postMessage?
Since the latter one could need cross-process messaging, I think.

Comment 4

[Johnny Stenback (:jst)]

Yeah, I think the only postMessage() method that needs e10s love is the one on shared workers, which we don't implement yet.

Comment 5

[Gabor Krizsanits (INACTIVE)]

(In reply to Johnny Stenback  (:jst, [e-mail]) from comment #4)
> Yeah, I think the only postMessage() method that needs e10s love is the one
> on shared workers, which we don't implement yet.

I think for shared workers first we need to figure out how to share them between multiple content processes. Any other approach would probably be a spec violation and a hack. I think making sure that worker.port.postMessage does what it supposed to do should be part of that work. Ben, is someone working on that / is there a bug filed for that?

Comment 6

[Ben Kelly [:bkelly, not reviewing]]

Not directly, but a lot of the infrastructure we need for service worker will make doing this for SharedWorker easier.  Marking the appropriate bugs as dependencies.

Comment 7

[Andrea Marchesini [:baku]]

worker.port.postMessage for SharedWorker is already multi-e10s compatible.
Internally SharedWorker ports are MessagePort.

Comment 8

[Andrea Marchesini [:baku]]

If this bug is just about SharedWorker.port.postMessage, it's already fixed by bug 1204775.