[Bug 27488] Steps 14-5 and 17-5 of the DOM 4 Range cloning algorithm appear to be incorrect.

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

--- Comment #5 from donjjordan@gmail.com ---
Yes. I was going to bring that up, but you beat me to it. :) 

I'm in the finishing stages of writing an implementation of the DOM 4
specification, from scratch, in "Modern" C++ for a project at work. All the
classes have a full suite of tests for them as well. I've combed over just
about every word in your new write-up of the specification. So, basically, I've
been idiot testing the document for the past 4 months. I have everything
implemented except for the MutationObservers (which I am working on now) and
the match method in the Element interface. I have to delve into the CSS
selector queries for that. I'm also planning to to make my DOM implementation
thread safe.  I've been busy.

The Range class was the only one that I had some difficulty with and I do have
a couple of questions regarding it. That's why I asked about a forum or
something of the same sort.

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

Received on Monday, 8 December 2014 22:17:58 UTC