Bug #2913
closed
http://www.saxonica.com/saxon-js/documentation/ does not work with Edge
Fix Committed on JS Branch:
0.9
Description
When I load http://www.saxonica.com/saxon-js/documentation/ with Edge on Windows 10, it shows "Loading documentation... " but no content.
If I reload with the developer console open then it shows a Javascript error
SCRIPT5002: Function expected
SaxonJS.min.js (1,5693)
so it seems the code does so far not work with Edge.
Edge identifies itself as
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/51.0.2704.79 Safari/537.36 Edge/14.14393
in @navigator.userAgent@.
Thanks, yes, this is a known limitation of the current Saxon-JS beta release.
- Status changed from New to In Progress
- Assignee set to Debbie Lockett
- Found in version set to 0.9
Initial testing on Windows browsers shows that the first problem is the use of the "new DocumentFragment()" constructor. Mozilla (MDN) labels this as experimental, and shows that it is not compatible with IE (and apparently not Edge either). We should be able to instead create an empty DocumentFragment using the document.createDocumentFragment method.
Updates committed to replace use of 'new DocumentFragment' by 'document.createDocumentFragment', as suggested above. This seems to get the documentation running on Windows browsers. Further testing required to check for other issues.
One issue I notice is that the highlighting of search results is not working. This seems to be because the function findit in jstree.js begins:
if (window.find) { ...
but apparently window.find is nonstandard (and not supported in Windows browsers).
- Status changed from In Progress to Resolved
Further testing has been done with IE and Edge. These browsers will be supported in the next release.
The documentation viewer app will also be updated. In particular the search mechanism is moved from JS to XSLT, so window.find is no longer used, which fixes the problem with highlighting search results.
- Status changed from Resolved to Closed
- % Done changed from 0 to 100
- Fixed in version set to 0.9.1
Bug fix applied in the Saxon-JS 0.9.1 beta release.
- Fixed in JS Release set to Saxon-JS 0.9.1
- Applies to JS Branch 0.9 added
- Fix Committed on JS Branch 0.9 added
Please register to edit this issue
Also available in: Atom
PDF
Tracking page
.