Re: [dom] The "replace" algorithm doesn't deal with the case when child == node.prevSibling

On Sun, Jun 3, 2012 at 10:11 PM, Boris Zbarsky <bzbarsky@...> wrote:
> No problem.  I was rejiggering the Gecko insert/replace code a bit, and
> figured I should just write it step by step per spec was all.  :)

FYI, it looks like the replace steps had a redundant check (Ms2ger
pointed it out so you might already know):

https://bitbucket.org/ms2ger/dom-core/changeset/bd54554371e3


--
Anne — Opera Software
http://annevankesteren.nl/
http://www.opera.com/