Add constructor to DocumentFragment interface

Confirmed Issue #9628204 • Assigned to Nishant S.


Andrii D.
Nov 2, 2016
This issue is public.
Found in
  • Microsoft Edge
  • Internet Explorer
Standard affected

Found in build #
Reported by 1 person

Sign in to watch or report this issue.

Steps to reproduce

W3C Recommendation on DOM Level 4 and WHATWG DOM Standard states that DocumentFragment can be used as constructor and return new DocumentFragment node.
Unfortunately Edge throws an error even on simple code which hurts interoperability with other browsers (Chrome, Firefox).

Problem code
var tree = new DocumentFragment();
Desired behavior: tree should be new DocumentFragment node

Current behavior: Edge shows error
Function expected


0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Ibrahim O.”

      Changed Assigned To to “Travis L.”

      Changed Status to “Confirmed”

      Changed Title from “Unable to call DocumentFragment as a constructor” to “Unable to call DocumentFragment as a constructor”

      Changed Title from “Unable to call DocumentFragment as a constructor” to “Add constructor to DocumentFragment”

      Changed Title from “Add constructor to DocumentFragment” to “Add constructor to DocumentFragment interface”

      Changed Steps to Reproduce

      Changed Assigned To from “Travis L.” to “Kris K.”

      Changed Assigned To from “Kris K.” to “Fei W.”

      Changed Assigned To from “Fei W.” to “Nishant S.”

      Changed Steps to Reproduce

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

    Sign in