873020 - [Workers] importScriptsIn()

Status: RESOLVED WONTFIX

(Core :: DOM: Workers, defect)

Description

[David Teller [:Yoric] - still alive but not very active]

To implement a module loader for workers (bug 872421), it would be extremely useful to have the following global function:

importScriptsIn(object, url1, url2, ...)
// Load and execute scripts at url1, url2, ..., as |importScripts| but add any toplevel value as fields of |object|, instead of the worker scope.

Comment 1

[Ben Turner (not reading bugmail, use the needinfo flag!)]

This would need to be proposed to the [e-mail] mailing list.

Comment 2

[David Teller [:Yoric] - still alive but not very active]

Well, for the moment, I am more concerned with chrome workers, so I would be satisfied with having |mozImportScriptsIn()|.

But if you want, I can submit to w3 or whatwg.

Comment 3

[Ben Turner (not reading bugmail, use the needinfo flag!)]

Yeah, ChromeWorker shouldn't diverge from Worker unless there are security concerns imo.

Comment 4

[David Teller [:Yoric] - still alive but not very active]

I have found how to almost encode the behavior I need using importScripts(), XMLHttpRequest, URL.createObjectURL() and a few tricks. The only thing I seem to be missing is having the right names in fields .fileName and .stack. I can live with this for the moment.