XML5602: Unexpected end of input error logged in IE11 and Edge
Created by: vegasmurphy
Environment
-
The MPD passes the DASH-IF Conformance Tool on http://dashif.org/conformance.html -
The stream has correct Access-Control-Allow-Origin headers (CORS) -
There are no network errors such as 404s in the browser console when trying to play the stream -
The issue observed is not mentioned on https://github.com/Dash-Industry-Forum/dash.js/wiki/FAQ -
The issue occurs in the latest reference client on http://dashif.org/reference/players/javascript/ and not just on my page
- Link to playable MPD file: Any valid file
- Dash.js version: >2.0 (Wasn't happening in dash 1.5 with old version of xml2json)
- Browser name/version: IE11 Edge
- OS name/version: Windows 10
Steps to reproduce
- Load any valid media into the dash mediaplayer
- In IE11 and Edge a XML5602: Unexpected end of input error will be logged
Observed behaviour
In IE11 and Edge a XML5602: Unexpected end of input error will be logged
In the xml2json library in the parseXmlString function there is a call to parsererrorNS = parser.parseFromString("INVALID", "text/xml").getElementsByTagName("parsererror")[0].namespaceURI;
This throws an error in IE11 and Edge.
I don't see any reason for getting the parsererror namespace and then searching for it in the xmlDoc that results from parsing the actual xml as opposed to just searching for the parsererror element directly. I logged an issue with xml2json as well to see whether there is a reason behind using the namespace to discover errors: https://github.com/abdmob/x2js/issues/41