Re: [w3c/ServiceWorker] Service worker MessageEvents set the "origin" property, but Worker MessageEvents do not. (#1122)

asutherland left a comment (w3c/ServiceWorker#1122)

Replying to https://github.com/w3c/ServiceWorker/issues/1122#issuecomment-296311526
> I'd love to hear if there are any implementation issues in Gecko that would make passing the origin tricky (and if so, help explain why the spec doesn't do it), or if it'd be a straightforward change to start passing an origin everywhere.

This would be a straightforward change in gecko.  [Here is where we pass an empty origin for to-parent messages](https://searchfox.org/firefox-main/rev/28398d11d39984cc5db08020671e7dd0d1408ec0/dom/workers/MessageEventRunnable.cpp#167-170) and [here is where we pass an empty origin for to-worker messages](https://searchfox.org/firefox-main/rev/28398d11d39984cc5db08020671e7dd0d1408ec0/dom/workers/MessageEventRunnable.cpp#72-75).  I have not done the archeology but presumably the assumption was that since workers are required to be same origin it was silly to pass it; the existence of web extension content scripts has of course clouded that situation slightly.



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3c/ServiceWorker/issues/1122#issuecomment-3755682510
You are receiving this because you are subscribed to this thread.

Message ID: <w3c/ServiceWorker/issues/1122/3755682510@github.com>