Menu

#65 Add XSLTProcessor workaround for Microsoft Edge

v1.0 (example)
closed-fixed
nobody
None
5
2017-06-08
2016-03-19
Volkert
No

While running the Sarissa unit tests in my Sarissa branch on GitHub, I noticed that 5 out of 8 tests in XSLTProcessorTestCase were failing in Microsoft's new Edge browser that comes with Windows 10. I did some Googling on this and if I understand correctly, the cause of those test failures is a known issue with Edge, so Sarissa is probably not to blame for that. Also, all other tests pass in Edge without problems. I provided a screenshot of the test failures in Microsoft Edge.

Would it perhaps be possible to implement some kind of workaround for this apparent browser limitation in Sarissa?

For more details about the XSLT Processor issue in Microsoft Edge, see the following Feedback tickets at Microsoft Connect:

By the way, for those who don't yet know it, it is not necessary to purchase any Windows licenses in order to develop, test, and/or debug sites and scripts with Microsoft Edge. Microsoft has freely and legally made cross-platform VM images available for exactly those purposes. I was using such a VM myself to run the Sarissa tests on when I encountered this issue. These VM images be downloaded here: https://dev.windows.com/en-us/microsoft-edge/tools/vms/windows/

1 Attachments

Discussion

  • Volkert

    Volkert - 2016-09-24

    This bug is said to be fixed in a recent update for Microsoft Edge as of September 2016, according to the comments at the bottom of this issue: https://developer.microsoft.com/en-us/microsoft-edge/platform/issues/8598827/ I haven't tested this yet.

     
  • Emmanuil Batsis (Manos)

    • status: open --> closed-fixed
     
  • Emmanuil Batsis (Manos)

    fixed in CVS

     

Log in to post a comment.