W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2011

[Bug 15194] New: Insertion of a DocumentFragment underspecified

From: <bugzilla@jessica.w3.org>
Date: Thu, 15 Dec 2011 00:52:44 +0000
To: www-dom@w3.org
Message-ID: <bug-15194-4009@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=15194

           Summary: Insertion of a DocumentFragment underspecified
           Product: WebAppsWG
           Version: unspecified
          Platform: PC
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: DOM Core
        AssignedTo: annevk@opera.com
        ReportedBy: adamk@chromium.org
         QAContact: member-webapi-cvs@w3.org
                CC: mike@w3.org, www-dom@w3.org


In "Mutation Algorithms"
(http://dvcs.w3.org/hg/domcore/raw-file/tip/Overview.html#mutation-algorithms),
step 4 of the "insert" algorithm says:

"If node is a DocumentFragment node, insert its children (preserving tree
order), before child or at the end of parent if child is null." [note that
"insert" is not hyperlinked to anything]

Should "insert its children" instead read "pre-insert its children"? In
particular, I'm interested in when the children are meant to be disconnected
from the DocumentFragment; are they removed all at once, then inserted
one-by-one, or do they simply get removed as part of pre-insert step (6) (Adopt
)?

For the purposes of MutationObservers, it would be convenient if the
DocumentFragment's children were removed all at once, though that doesn't match
the current WebKit behavior (I haven't looked at other implementations yet).

-- 
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, 15 December 2011 00:52:46 GMT

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