there is no "window" inside WebWorker

Question

there is no "window" inside WebWorker

Yaffle opened this issue 13 years ago · 16 comments

Answer 1 · 2011-09-22T14:33:26.000Z

I cannot see how the title you have given this (empty) issue applies at all to our setImmediate implementation. Please explain and I will reopen if it makes sense.

Answer 2 · 2011-09-22T14:58:09.000Z

index.html:

var x = new Worker('webworker.js');

webworker.js:

setImmediate(....); -> window is undefined....

Answer 3 · 2011-09-22T16:04:36.000Z

OK, I think I have a working implementation of setImmediate for web worker use; it works inside the latest stable Chrome and Firefox. Can you test my fork at https://github.com/DomenicDenicola/setImmediate and see if it's working as expected? If so I will pull it back into the NobleJS repository.

Answer 4 · 2011-09-22T16:37:36.000Z

it works good
Opera 11 and Chrome 14 tested

see my test files here:
https://gist.github.com/1235275

Answer 5 · 2011-09-22T16:40:21.000Z

Also, It seems, Firefox 6 hasn't minimum delay for setTimeout, so setTimeout(..., 0) works as setImmediate
in Workers

Answer 6 · 2011-09-22T16:48:25.000Z

but some problems with setImmediate undef IE8 ...

Answer 7 · 2011-09-22T17:06:49.000Z

According to http://caniuse.com/#webworkers IE doesn't support web workers until IE10.

Answer 8 · 2011-09-22T17:12:24.000Z

i know, i test outside worker, on single page,
IE 8 standart mode

Answer 9 · 2011-09-22T17:43:02.000Z

I believe the problem here is that postMessage doesn't work properly with local files in IE8. Are you testing locally, or with a web server?

Answer 10 · 2011-09-22T18:08:35.000Z

http://localhost

it will be good to create some tests in repo

Answer 11 · 2011-09-22T18:10:29.000Z

Darn, OK. Do you know if the NobleJS setImmediate (i.e. not the one in my fork) works in IE8 on localhost? I'm trying to figure out if the changes in the fork broke it, or if it's never worked there.

Answer 12 · 2011-09-22T18:17:33.000Z

i can't test it now, i'll try later

Answer 13 · 2011-09-23T04:35:06.000Z

changes in fork doesn't broke it!

in master repo (and fork too)
there are 3 mistakes:

window.attachEvent("message", handleMessage);

should be
window.attachEvent("onmessage", handleMessage);

in IE event.source !== window
is "event.source === window" usefull ?

3);
IE8 postMessage is synchronous
so it can't be used to emulate setImmediate
http://www.google.ru/search?client=opera&rls=ru&q=IE8+postMessage+is+synchronous&sourceid=opera&ie=utf-8&oe=utf-8&channel=suggest

Answer 14 · 2011-09-23T04:44:23.000Z

Seems,

you meen "Doen setImmediate is syncronouse/asyncronouse" in use test/test.js:

"Does setImmediate yield to subsequent code before executing its callback"

Answer 15 · 2011-09-23T06:51:18.000Z

var syncronouse = false;
function atest() {
syncronouse = true;
};
window.onmessage = atest;
window.postMessage('', '*');
window.onmessage = null;
if (synconouse) {
can't use postMessage for setImmediate
}

Answer 16 · 2011-09-23T16:05:37.000Z

Thanks Yaffle! I did a major refactor incorporating your fixes; IE8 now falls back to setTimeout(..., 0) and has been tested to work. I'll look at your pull request later to hopefully incorporate some of those tests into the repository as well.