14220 2011-09-19 13:59:17 +0000 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-20 08:33:57 +0000 1 1 1 Unclassified WebAppsWG Web Workers (editor: Ian Hickson) unspecified Other other RESOLVED INVALID http://www.whatwg.org/specs/web-apps/current-work/#top P3 normal --- 1 contributor ian art.barstow mike public-webapps public-webapps-bugzilla oldest_to_newest 56992 0 contributor 2011-09-19 13:59:17 +0000 Specification: http://www.w3.org/TR/2011/WD-workers-20110901/ Multipage: http://www.whatwg.org/C#top Complete: http://www.whatwg.org/c#top Comment: 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 mistaken. Some browsers (Firefox?) have one thread for all pages. They cannot support two threads both accessing DOMs, even different DOMs, because their implementation is not thread-safe at all. Different pages can both access DOMs because they're actually on the same thread. (I think.) --------- You may be right about the single thread. Also it appears that Firefox does not allow one to start another instance of it as another process. Even with 3 running, there is only a single firefox in the process list. In such a situation, I would recommend that Firefox be changed rather than the spec. Posted from: 199.89.158.130 User agent: Mozilla/5.0 (compatible; MSIE 9.0; Windows NT 6.1; WOW64; Trident/5.0) 57022 1 zcorpan 2011-09-20 08:33:57 +0000 Please get a bugzilla account and use bugzilla correctly.