W3C home > Mailing lists > Public > www-dom@w3.org > October to December 2013

[Bug 23565] cloneNode IDL does not match reality

From: <bugzilla@jessica.w3.org>
Date: Mon, 21 Oct 2013 14:52:12 +0000
To: www-dom@w3.org
Message-ID: <bug-23565-4009-0lru4mwxSV@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23565

Boris Zbarsky <bzbarsky@mit.edu> changed:

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

--- Comment #5 from Boris Zbarsky <bzbarsky@mit.edu> ---
> OK. I'll update Blink.

There should be no need to change anything in Blink.

This testcase:

<body><script>
  alert(document.body.cloneNode(undefined).childNodes.length);
  alert(document.body.cloneNode().childNodes.length);
</script>

already alerts "0" and then "2" in my Chrome dev build (32.0.1671.3), which is
what the DOM spec _used_ to require before the WebIDL changes to how undefined
is handled, and is also what the DOM spec should imo specify once this bug is
fixed.

Anne, your changes aren't what this bug was asking for.  What this bug is
asking for is:

  Node cloneNode();  // deep clone specified in prose
  Node cloneNode(boolean deep);

and similar for importNode.

Reopening, since as far as I can tell the intent of the desired change was
totally misunderstood.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
Received on Monday, 21 October 2013 14:52:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:21 UTC