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

On Thu, Jun 14, 2012 at 9:42 PM, Boris Zbarsky <bzbarsky@mit.edu> wrote:

> 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).


I'm OK leaving the spec as is and changing WebKit if you feel strongly
about this. It just seemed like a silly requirement to add extra code for.


>  Does that answer your question?
>>
>
> Yep.
>
> -Boris
>