Javascript not resolving worker path relative to current script

javascript web-worker
Matt Diamond picture Matt Diamond · Sep 14, 2012 · Viewed 8.9k times · Source

I have a script at http://localhost/js/foo.js which needs to spawn a Web Worker from the file http://localhost/js/fooWorker.js. I assumed I could just do something like this:

var worker = new Worker('fooWorker.js')

However, this results in a 404 error, as the browser cannot find http://localhost/fooWorker.js. I was under the impression that worker paths were resolved relative to the script spawning the worker, so shouldn't I just be able to specify the name of another .js file in the same directory without having to provide an absolute path? Am I doing something wrong?

Answer

Ilia Frenkel picture Ilia Frenkel · Sep 14, 2012

From http://www.w3.org/TR/workers/:

When the Worker(scriptURL) constructor is invoked, the user agent must run the following steps:

  1. Resolve the scriptURL argument relative to the entry script's base URL, when the method is invoked.

Related questions

Web workers without a separate Javascript file?

As far as I can tell, web workers need to be written in a separate JavaScript file, and called like this: new Worker('longrunning.js') I'm using the closure compiler to combine and minify all my JavaScript source code, and …

Read More
Chrome can't load web worker

I am working on a project that uses a web worker. In my head section I have this code: var worker = new Worker("worker.js"); // More code This works fine in Safari, but Chrome reports the following error: Uncaught SecurityError: …

Read More
Uncaught ReferenceError: importScripts is not defined

Why do I keep getting this error? I should be able to use this global function right? http://www.html5rocks.com/en/tutorials/workers/basics/ I'm using chrome. I'm using https://code.google.com/p/bitjs/ and it begins …

Read More