[Bug 17541] Carefully think through how Range.insertNode should behave when the node to be inserted is already at the beginning of the range from bugzilla@jessica.w3.org on 2014-02-13 (public-webapps-bugzilla@w3.org from February 2014)

From: <bugzilla@jessica.w3.org>
Date: Thu, 13 Feb 2014 16:27:33 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-17541-2532-VFM147m0es@http.www.w3.org/Bugs/Public/>

https://www.w3.org/Bugs/Public/show_bug.cgi?id=17541

Anne <annevk@annevk.nl> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |bugs@pettay.fi

--- Comment #1 from Anne <annevk@annevk.nl> ---
I don't really understand what is going on here. E.g. if I change the 2 in the
setStart() call to 3 or 1 the result is still the same in Gecko. I don't know
why.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 13 February 2014 16:27:35 UTC