[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-04-24 (public-webapps-bugzilla@w3.org from April 2014)

From: <bugzilla@jessica.w3.org>
Date: Thu, 24 Apr 2014 13:23:29 +0000
To: public-webapps-bugzilla@w3.org
Message-ID: <bug-17541-2532-4PDMXzxDxA@http.www.w3.org/Bugs/Public/>

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

--- Comment #9 from Anne <annevk@annevk.nl> ---
Are implementers interested in maintaining that as well? Note that we already
have two algorithms (in pre-insert and replace) for checking that are much
alike, but different due to context.

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

Received on Thursday, 24 April 2014 13:23:32 UTC