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

Re: [DOM4] Mutation algorithm imposed order on document children

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Fri, 15 Jun 2012 00:42:29 -0400
Message-ID: <4FDABD35.8010503@mit.edu>
To: Ojan Vafai <ojan@chromium.org>
CC: Anne van Kesteren <annevk@annevk.nl>, Elliott Sprehn <esprehn@gmail.com>, Ryosuke Niwa <rniwa@webkit.org>, www-dom <www-dom@w3.org>
On 6/14/12 11:43 PM, Ojan Vafai wrote:
> This is the only case I know of in the DOM apis where we enforce
> ordering. So, right now, WebKit just has a canAcceptChild method that
> takes a pointer to the new child. It doesn't need to know where that
> child is going.

Unless we're talking about replaceChild, right?  In which case you do 
need to care what's being replaced (and in fact you have code in 
Document::checkReplaceChild which very much cares, at first glance).

> Does that answer your question?


Received on Friday, 15 June 2012 04:42:59 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:37:00 UTC