* Fix for https://github.com/futurepress/epub.js/issues/537
Following are the changes for getting IE and Firefox working:
• src doc is not supported in IE which was used to render the page content. Now changed the condition if src doc is supported or not and if not we are writing html string to the iframe using iframe.write api.
• Was using page response as xml(responseXML property of xhr), which was creating issue of self closing tags in IE and page was not getting rendered.
Now we have done changes to make use of string output of response to render(using responseText property of xhr) which don't have self closing tags.
• We were not able to load the css and js present in the page contents if they carried a relative URL.
To fix it we have added base tag into the html head so that the js and css links can be found.
• Was using treewalker dom api. In IE expects that acceptNode param should be a function but other browsers expects it to be an object. We have fixed it .
• treewalker dom api has problem with IE if we are passing a text node as root node(throws exception on treewalker.nextNode(), other browsers it returns null). Have added a condition to fix it(if text node do not create treewalker)
* Review change: removed base tag as its being added using hook
* PR changes: reverted the request method implementation and xmlSerialization implementation
* reverted the request method changes to return the response object, now xml is returned
* Updated the condition for IE to use xmldom
Review comment change: To resolve IE self closing tag issue(which causes rendering issue in IE), made use of xmldom npm package.
* Removed a not necessary condition in next() that stops single column layout from going to next chapter.
* Add loading on next chapter togather with scrollto that avoids over scrolling the end of chapter
