Using document.createDocumentFragment().cloneNode() creates DOCUMENT_NODE instead of DOCUMENT_FRAGMENT_NODE.

Confirmed Issue #8619646 • Assigned to Travis L.


Krzysztof K.
Aug 24, 2016
This issue is public.
Found in
  • Microsoft Edge
Found in build #
Reported by 5 people

Sign in to watch or report this issue.

Steps to reproduce

As mentioned in the issue title, running the code (even in the dev console):


creates a node with nodeType == Node.DOCUMENT_NODE, while it should create document fragment node (nodeType == Node.DOCUMENT_FRAGMENT_NODE).

This issue started occurring on newest Edge version (38).


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Travis L.”

      Changed Assigned To from “Travis L.” to “Eugene V.”

      Changed Status to “Confirmed”

      Changed Assigned To from “Eugene V.” to “Sanket J.”

      Changed Assigned To from “Sanket J.” to “Jose L.”

    • This is a very serious issue. Can we expect it to be fixed in the next Edge release? And when will this happen?

    • Microsoft Edge Team

      Changed Assigned To from “Jose L.” to “Arron E.”

    • I checked it twice with the same Windows 10 virtual machine image downloaded from This bug appears after setting up the machine, but when OS gets updated (even though the Edge version (38.14393 / 14.14393) did not change) the bug does not appear anymore and everything works as expected. Can you recheck it on your side?

      If it may be helpful, the Windows 10 VM image checksum is 9a1d638d51211114fc4f22735c3f26d3fe8951ca.

    • Microsoft Edge Team

      Changed Assigned To from “Arron E.” to “Travis L.”

    You need to sign in to your Microsoft account to add a comment.

    Sign in