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

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

From: Anne van Kesteren <annevk@annevk.nl>
Date: Mon, 4 Jun 2012 10:38:02 +0200
Message-ID: <CADnb78iCd5J6UoNG23gTxQCyfa-3m3iJ0W3epPm7b80-Q455gw@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: www-dom@w3.org
On Sun, Jun 3, 2012 at 10:11 PM, Boris Zbarsky <bzbarsky@mit.edu> 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/
Received on Monday, 4 June 2012 08:43:37 GMT

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