W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

[Bug 14220] New: 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

From: <bugzilla@jessica.w3.org>
Date: Mon, 19 Sep 2011 13:59:17 +0000
To: public-webapps@w3.org
Message-ID: <bug-14220-2927@http.www.w3.org/Bugs/Public/>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=14220

           Summary: 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
           Product: WebAppsWG
           Version: unspecified
          Platform: Other
               URL: http://www.whatwg.org/specs/web-apps/current-work/#top
        OS/Version: other
            Status: NEW
          Severity: normal
          Priority: P3
         Component: Web Workers (editor: Ian Hickson)
        AssignedTo: ian@hixie.ch
        ReportedBy: contributor@whatwg.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, public-webapps@w3.org


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)

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.
Received on Monday, 19 September 2011 13:59:20 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:47 GMT