1334891 - Support Web Workers created from content scripts

Status: REOPENED

(WebExtensions :: General, enhancement, P5)

Description

[Philipp Kewisch [:Fallen] [:📆][:🧩]]

When creating a new Worker from a content script, it seems to use the same origin as the page and possibly creates the worker in page context. Instead, the Worker should be created with the origin/context of the content script.

It is therefore not possible to do new Worker(chrome.runtime.getURL('worker.js')), which results in SecurityError: Failed to load worker script at "moz-extension://ffb83def-dae7-3343-9063-794353cf4b9a/worker.js".

This also does not work in Chrome, but it would be great if it does in Firefox. See http://crbug.com/357664

Comment 1

[:shell escalante]

kris is filing corresponding platform bug

Comment 3

[Rob Wu [:robwu]]

Kris, can you explain why you marked this as a duplicate of bug 1260548? That other bug does not seem to be very relevant.

Comment 4

[Kris Maglione [:kmag]]

I didn't intend to.

Comment 6

[Rob Wu [:robwu]]

Bug 1423442 has a test case.

A partial work-around is to fetch the script text and then create a worker from the script URL: https://stackoverflow.com/questions/10343913/how-to-create-a-web-worker-from-a-string

This work-around is imperfect, because it is subject to the page's Content Security Policy.
For example, run this from a content script on Github (which has a restrictive CSP):

    new Worker(URL.createObjectURL(new Blob(['console.log("test");close()'])))

Tested with Nightly 61.0a1, 2018-04-29, the output in the tab's console is:
Content Security Policy: The page's setings blocked the loading of a resource at blob:https://github.com/[UUID] ("script-src")

Comment 7

[Firefox Bug Husbandry Bot]

Bulk move of bugs per https://bugzilla.mozilla.org/show_bug.cgi?id=1483958