W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2012

[Bug 16638] New: Define who owns what with MutationObserver

From: <bugzilla@jessica.w3.org>
Date: Thu, 05 Apr 2012 06:33:23 +0000
To: www-dom@w3.org
Message-ID: <bug-16638-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=16638

           Summary: Define who owns what with MutationObserver
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM
        AssignedTo: annevk@opera.com
        ReportedBy: Olli.Pettay@gmail.com
         QAContact: public-webapps-bugzilla@w3.org
                CC: mike@w3.org, jonas@sicking.cc, www-dom@w3.org,
                    adamk@chromium.org, rafaelw@chromium.org


Should MutationObserver own the nodes it is observing?
I think not. If JS doesn't have a pointer to the node, it can't
modify it.
But if the original observe target is deleted, what should happen
to the transient observers? I think they should still work (until the end of
the microtask). That way GC/CC behavior isn't visible to the API user.

Then MutationObserver object itself... I think the only way to hide GC/CC
behavior is to keep MutationObserver object alive as long as
the node(s) it is observing is/are alive.

-- 
Configure bugmail: https://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 Thursday, 5 April 2012 06:33:26 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:09 GMT