[Webkit-unassigned] [Bug 123565] Expose DOM4 ParentNode API on Document, Element, and DocumentFragment

[bugzilla-daemon at webkit.org]

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

Chris Dumez <cdumez at apple.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #7 from Chris Dumez <cdumez at apple.com> ---
I have just compared our implementation with the specification and it does appear that:
- Our ParentNode.idl matches the DOM spec at https://dom.spec.whatwg.org/#parentnode
- Document, DocumentFragment and Element implement ParentNode

So I think we can close this bug.

Also not that actual naming we use does not matter that much since the 'ParentNode' naming is not web-exposed. That said, there are advantages to matching the naming in the spec.

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.webkit.org/pipermail/webkit-unassigned/attachments/20160411/2b39346d/attachment-0001.html>