« Return to Thread: [Bug 16638] New: Define who owns what with MutationObserver

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

by Bugzilla from bugzilla@jessica.w3.org :: Rate this Message:

| View in Thread

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@...
        ReportedBy: Olli.Pettay@...
         QAContact: public-webapps-bugzilla@...
                CC: mike@..., jonas@..., www-dom@...,
                    adamk@..., rafaelw@...


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.

 « Return to Thread: [Bug 16638] New: Define who owns what with MutationObserver