Re: Query on DOM range methods
bhanukrushna rout <[email protected]>
| Newsgroups | gmane.comp.web.dom.general |
|---|---|
| Message-ID | <[email protected]> |
Hi, In chromium code base, I notice null parent check is added as mentioned in DOM4 spec (http://dom.spec.whatwg.org/). root container and refNode constraint is retained as given in DOM2 spec (http://www..w3.org/TR/DOM-Level-2-Traversal-Range/ranges.html) . Additionally, element node is allowed to be a root container. The element node's eligibility to become a root container is to fix the range method failure with detached node, also an issue in webkit that I am looking at. But, this requirement is nowhere mentioned in any of the specs. Chromium code for reference : https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/Source/core/dom/Range.cpp&q=range.cpp&sq=package:chromium Now, I am confused if a particular spec revision is complete in itself or its a change in addition to the previous revisions. Please help me understand it and let me know if element node to be allowed as a root container. Thanks, Bhanu On Thursday, 30 January 2014 11:32 PM, Anne van Kesteren <[email protected]> wrote: On Wed, Jan 29, 2014 at 10:19 PM, bhanukrushna rout<[email protected] > wrote:> Since, my changes are highly dependent on these specification changes, I> just want to confirm if my understanding about the latest specification is> correct before making any changes. Let me know if I need to focus on any> other thing which I might have missed mentioning above and not part of> current behaviour.I believe they should be correct, unless Aryeh says otherwise. If youfind that browsers do not match http://dom..spec.whatwg.org/ theremight be a problem.-- http://annevankesteren.nl/