[Webkit-unassigned] [Bug 141199] New: Range startContainer can't access parent 3 levels up in a contentEditable

bugzilla-daemon at webkit.org bugzilla-daemon at webkit.org
Tue Feb 3 09:45:59 PST 2015


https://bugs.webkit.org/show_bug.cgi?id=141199

            Bug ID: 141199
           Summary: Range startContainer can't access parent 3 levels up
                    in a contentEditable
    Classification: Unclassified
           Product: WebKit
           Version: 528+ (Nightly build)
          Hardware: Unspecified
                OS: Unspecified
            Status: NEW
          Severity: Normal
          Priority: P2
         Component: HTML Editing
          Assignee: webkit-unassigned at lists.webkit.org
          Reporter: sirisian at gmail.com

So startContainer in the range object behaves rather funny. It's like a pseudo element. === randomly fails when comparing to the DOM element got by getElementById, but .isEqualNode will always work. This might be correct to the spec I'm not sure, but one oddity in Webkit is that you can only access 2 parents up. If you do something like:

range.startContainer.parentNode.parentNode.parentNode it returns null. If you get the element startContainer is referencing and do element.parentNode.parentNode.parentNode it returns the correct DOM element. Very odd behavior.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.webkit.org/pipermail/webkit-unassigned/attachments/20150203/742bd391/attachment-0002.html>


More information about the webkit-unassigned mailing list