9823
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
LATE
|
Add "maxExecutionContexts" property with number of hardware execution contexts
|
2010-05-28
|
2010-08-27
|
10420
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
NEED
|
Can you post sample of cross domain for web workers?
|
2010-08-24
|
2010-09-25
|
11818
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
LATE
|
As documented in the "Creating workers" section, a worker *must* be an external script. This prevents developing or deploying code that uses Web Workers as a single page app, which is often quite handy. Could this restriction be lifted?
|
2011-01-20
|
2011-02-16
|
11827
|
WebAppsW
|
Web Work
|
ian
|
CLOS
|
WORK
|
[Workers] "connect" event interface type not defined
|
2011-01-21
|
2011-02-02
|
12067
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Improve error handling in workers
|
2011-02-14
|
2011-06-21
|
12340
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
It is not clear which worker to use when using nameless SharedWorker
|
2011-03-19
|
2011-06-21
|
12574
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
AbstractWorker and WorkerGlobalScope should inherit EventTarget
|
2011-04-29
|
2011-08-05
|
12836
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
WorkerLocation lacks a strigifier
|
2011-05-31
|
2011-06-21
|
12941
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
If I understand what I'm reading correctly, there's an error at the end of "A background number-crunching worker" tutorial. I think you mean "postMessage()" instead of "send()" in the sentence "To send a message back to the page, the send() method is used
|
2011-06-11
|
2011-06-21
|
13063
|
WebAppsW
|
Web Work
|
ian
|
CLOS
|
FIXE
|
MessagePort normatively referenced by not defined
|
2011-06-26
|
2011-08-10
|
13064
|
WebAppsW
|
Web Work
|
ian
|
CLOS
|
FIXE
|
WindowBase64 normatively referenced by not defined
|
2011-06-26
|
2011-08-10
|
13065
|
WebAppsW
|
Web Work
|
ian
|
CLOS
|
FIXE
|
WindowTimers normatively referenced by not defined
|
2011-06-26
|
2011-08-10
|
13146
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
hola como estan
|
2011-07-05
|
2011-07-05
|
13232
|
WebAppsW
|
Web Work
|
ian
|
CLOS
|
FIXE
|
I think the section on DedicatedWorkerScope should include information about the kinds of data that postMessage can send to a worker, and the kinds of data that a worker can send back. http://dev.w3.org/html5/workers/#dedicated-workers-and-the-dedicatedwo
|
2011-07-13
|
2011-08-19
|
13254
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
what the hell is this
|
2011-07-14
|
2011-07-14
|
13255
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
When I use importScripts in my worker to load a separate "library" file, it works, but I get the error: ReferenceError: Can't find variable: importScripts (Safari) Uncaught ReferenceError: importScripts is not defined So it's throwing an error, but that
|
2011-07-14
|
2011-08-08
|
13280
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Why isn't MessageEvent linked to a definition? It's not at all clear what this object is. And the postMsg API has a MessageEvent, but that object doesn't have the "target" property, which is used in the sample code below. A lot more information about Mess
|
2011-07-17
|
2011-07-17
|
13373
|
WebAppsW
|
Web Work
|
ian
|
VERI
|
FIXE
|
Privacy: Limit SharedWorker connections to same top-level domain
|
2011-07-26
|
2011-10-25
|
13426
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
NEED
|
"Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" — this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
|
2011-07-28
|
2011-08-08
|
13427
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
"Attempt to fetch each resource identified by the resulting absolute URLs, from the entry script's origin" — this makes it sound as if you should only fetch URLs frm that origin, which looking more closely isn't the meaning. This should be made more obv
|
2011-07-28
|
2011-07-28
|
13580
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
WORK
|
web workers postMessage
|
2011-08-03
|
2011-08-08
|
13772
|
WebAppsW
|
Web Work
|
ian
|
VERI
|
FIXE
|
Example code should contain a comma instead of semicolon: worker.port.postMessage({ foo: 'structured', bar: ['data', 'also', 'possible']});
|
2011-08-13
|
2011-10-06
|
13844
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
Does web work add complex to web?
|
2011-08-20
|
2011-08-22
|
13989
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Need a spec for ErrorEvent constructor
|
2011-09-01
|
2011-09-10
|
14086
|
WebAppsW
|
Web Work
|
contributor
|
RESO
|
WONT
|
When performing AJAX type queries, they are already asynchronous and already occur in another thread. However, I have found that parsing the XML reply and converting that to a representation usable by the javascript application can result in freezes to t
|
2011-09-08
|
2014-10-02
|
14093
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Just to throw out an idea, to allow use of the XML parser, and alert() for debugging, one could implement web workers as simply another open page in the browser, with full access to the DOM, etc, with the ability to communicate to the 'parent' by posting
|
2011-09-08
|
2011-09-13
|
14116
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Regarding a previous post, a browser could launch itself (CreateProcess() on Windows) again and pass say a port number, a URL, and a boolean flag to the spawned child process. The browser could then be modified to examine it's command line- if there are 3
|
2011-09-12
|
2011-09-13
|
14137
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Just want to add - don't get hung up on the process/thread stuff. It is just a metaphor. I don't really care how it is implemented. One could do it all in one process. The present design fits the process model nicely. There is no sharing of memory.
|
2011-09-13
|
2011-09-13
|
14138
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Lastly, to make clear. I am not proposing web workers share the DOM with the main thread. I am proposing the each web worker has it's own INDEPENDENT DOM. (No sharing of memory or DOMs between workers/main thread).
|
2011-09-13
|
2011-09-13
|
14214
|
WebAppsW
|
Web Work
|
contributor
|
RESO
|
FIXE
|
missing definition of Transferable
|
2011-09-19
|
2015-10-06
|
14220
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
In reply to comment #0) > Every browser that I know of can have two web pages open at once. Those 2 web > pages both have a DOM, they don't share a DOM. Some browsers implement this > as 2 different processes, some as 2 threads. This is where you're m
|
2011-09-19
|
2011-09-20
|
14296
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
sorry, does this work
|
2011-09-26
|
2011-09-28
|
14677
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
Hey, There! =D My name is Felipe. And I'm looking around this new tecnology. I'm really enjoying it.
|
2011-11-02
|
2011-11-02
|
15094
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
WONT
|
When creating a worker, it should be possible to assign some arguments to the constructor, or pass an init object like so: var worker = new Worker("someurl.js", { someData: "1234" }); The object passed could be made available as the current context (this.
|
2011-12-07
|
2011-12-14
|
15141
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
DedicatedWorkerGlobalScope IDL formatting is broken
|
2011-12-10
|
2011-12-14
|
15554
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
Hi, The article is very good. Also user can view. HTML5 Web Workers http://www.totaldotnet.com/Article/ShowArticle145_HTML5WebWorker.aspx
|
2012-01-14
|
2012-01-14
|
15917
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
prueba de uso de web broker
|
2012-02-06
|
2012-02-06
|
16461
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
what this is importent to me?
|
2012-03-21
|
2012-03-21
|
16665
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
INVA
|
kk gd df d fgd f gd gdg
|
2012-04-09
|
2012-04-09
|
16730
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
WORK
|
Shared workers - use .source instead of .ports[0] ?
|
2012-04-13
|
2012-07-13
|
18001
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Allow data: URL for new Worker(). Supported by Opera and Firefox.
|
2012-07-18
|
2012-09-16
|
18003
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Change use of "relevant namespace object" term re workers
|
2012-07-18
|
2012-09-14
|
18188
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
"relevant namespace object" is not defined in WebIDL anymore.
|
2012-07-18
|
2012-10-19
|
18189
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
WORK
|
"The DedicatedWorkerGlobalScope interface must not exist ..." s/interface/interface object/ ?
|
2012-07-18
|
2012-09-28
|
18218
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
DUPL
|
Within the workers text "list of active intervals" can be removed because it is the same as "list of active timers".
|
2012-07-18
|
2012-10-19
|
18275
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
equivanet -> equivalent
|
2012-07-18
|
2012-09-15
|
18289
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Support 'column' here for consistency with window.onerror?
|
2012-07-18
|
2013-03-21
|
21725
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
FIXE
|
Specify id for Step 1 of the Web Workers Processing Model
|
2013-04-17
|
2013-06-03
|
26957
|
WebAppsW
|
Web Work
|
ian
|
RESO
|
WONT
|
Allow sending DOM objects to Workers and expose a DOM (or DOM-like) interface to workers
|
2014-10-02
|
2014-10-09
|