Using Javascript and XSLTProcessor, Edge fails to run transformation of stylesheet having a DOCTYPE node

Fixed Issue #5552211


Nov 23, 2015
This issue is public.
Fixed in build #
Reported by 2 people

Sign in to watch or report this issue.

Steps to reproduce

Repro Steps:

  1. Load test in browser window with JavaScript enabled.
  2. Check display, on failure it says "Test failed. Created fragment is: null.", if the test succeeds, it says “Test succeeded.” and displays the result of the XSLT transformation, a paragraph with non-breaking space characters.
    Expected Results:
    The used JavaScript code should run the transformToFragment method successfully and return a document fragment node which can be inserted into the HTML document running the script code. Or, if the processing of the stylesheet failed, an error indicating the reason of the failure should be thrown.
    Actual Results:

Dev Channel specific:



0 attachments

    Comments and activity

    • Microsoft Edge Team

      Changed Assigned To to “Mara P.”

      Changed Assigned To to “Rico M.”

      Changed Assigned To from “Rico M.” to “Thomas M.”

      Changed Status to “Confirmed”

      Changed Status from “Confirmed”

      Changed Status to “In progress”

      Changed Status from “In progress” to “In code review”

      Changed Steps to Reproduce

      Changed Status from “In code review”

      Changed Status to “In code review”

      Changed Assigned To from “Thomas M.” to “IE S.”

      Changed Status from “In code review” to “Fixed”

      Changed Steps to Reproduce

      Changed Steps to Reproduce

    • Hello,

      Thank you for fixed this bug.
      When I load test url, I still have the problem.

      You have to do an update by window update ?
      Could you give me a date for this update ?

      Thank you


    • Hello,

      When I load test URL : from Edge on Windows 10, I have the problem : Test faild.

      Could you look again on your side ?

      Thank you


    • I’ve created a new report to get the proper attention.

    • Hello,

      Thank you for providing this information about the issue. We are pleased to report this feature is fixed in Edge 15063 and is available in our latest Creator’s Update build.

      Best Wishes,
      The MS Edge Team

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

    Sign in