I have been working on a webpage developed in a CMS through a bination of XSLT 1.0, JS and XML and have e across a page rendering problem specifically when accessing the (ASP.NET) webpage on the Windows 10 operating system through the Microsoft Edge (37.14316.1000.0) browser (Microsoft EdgeHTML 14.14316).
The Problem:
(Screenshot Captured from a Virtual Machine, using the before-mentioned conditions)
As you can clearly see, when you access my webpage using the before-mentioned conditions, the course page structure is broken up. It appears as though my XSLT file isn't being executed properly and a conflict is going on somewhere? This is majorly frustrating as the XSLT/JS/XML page works perfectly in all the previous Internet Explorer browser versions (all the way down to 7) plus the other leading modern browsers such as Chrome, Firefox, Opera and Safari.
Maddeningly, the page actually works on Windows 10 version 10.0.10240 Build 10240 Edge 20.10240.16384.0, but I believe this was the previous Edge browser release, so somewhere between the last browser version and this one, this rendering problem has suddenly surfaced?
The JS file which calls my XSLT/XML files using the XSLT/XML on the Client method is obviously working, as data is appearing within the page, but something is not right and I'm struggling to identify what is causing the issue?
I have tried playing about with the main CSS file but have ruled this out as the underlying cause.
Interestingly when going into the source code of my page through the in-built Edge development tools, I managed to identify that if I removed the form1 reference on line 55, just inside the opening <body> tag (i.e. <form method="post" action="/aatp/courses/crops/resource-capture-by-crops.aspx" id="form1">), the page instantly fixes itself and renders out properly, as experienced on all the other internet browsers.
Crazy??
Perhaps this POST <form1> call is in direct conflict with the GET request made by my JS file? The form1 call is a consequence of our CMS architecture, since our web pages are effectively one big form, so I can't get rid of this 'CMS produced code'.
Any suggestions or ideas for a fix would be greatly appreciated and weled!
I have been working on a webpage developed in a CMS through a bination of XSLT 1.0, JS and XML and have e across a page rendering problem specifically when accessing the (ASP.NET) webpage on the Windows 10 operating system through the Microsoft Edge (37.14316.1000.0) browser (Microsoft EdgeHTML 14.14316).
The Problem:
(Screenshot Captured from a Virtual Machine, using the before-mentioned conditions)
As you can clearly see, when you access my webpage using the before-mentioned conditions, the course page structure is broken up. It appears as though my XSLT file isn't being executed properly and a conflict is going on somewhere? This is majorly frustrating as the XSLT/JS/XML page works perfectly in all the previous Internet Explorer browser versions (all the way down to 7) plus the other leading modern browsers such as Chrome, Firefox, Opera and Safari.
Maddeningly, the page actually works on Windows 10 version 10.0.10240 Build 10240 Edge 20.10240.16384.0, but I believe this was the previous Edge browser release, so somewhere between the last browser version and this one, this rendering problem has suddenly surfaced?
The JS file which calls my XSLT/XML files using the XSLT/XML on the Client method is obviously working, as data is appearing within the page, but something is not right and I'm struggling to identify what is causing the issue?
I have tried playing about with the main CSS file but have ruled this out as the underlying cause.
Interestingly when going into the source code of my page through the in-built Edge development tools, I managed to identify that if I removed the form1 reference on line 55, just inside the opening <body> tag (i.e. <form method="post" action="/aatp/courses/crops/resource-capture-by-crops.aspx" id="form1">), the page instantly fixes itself and renders out properly, as experienced on all the other internet browsers.
Crazy??
Perhaps this POST <form1> call is in direct conflict with the GET request made by my JS file? The form1 call is a consequence of our CMS architecture, since our web pages are effectively one big form, so I can't get rid of this 'CMS produced code'.
Any suggestions or ideas for a fix would be greatly appreciated and weled!
Share Improve this question asked May 20, 2016 at 16:23 JoelJoel 2476 silver badges15 bronze badges 1-
Does it improve things if you put
<xsl:output method="html"/>in the XSLT? – Martin Honnen Commented May 20, 2016 at 16:51
1 Answer
Reset to default 4Try to convince Edge that the stylesheet creates HTML elements by putting <xsl:output method="html"/> into your XSLT stylesheet.