Bug #2913: http://www.saxonica.com/saxon-js/documentation/ does not work with Edge - SaxonJS - Saxonica Developer Community

Actions

Send by e-mail Copy link

Bug #2913

closed

http://www.saxonica.com/saxon-js/documentation/ does not work with Edge

Added by Martin Honnen over 8 years ago. Updated over 7 years ago.

Status:

Closed

Priority:

Low

Assignee:

Debbie Lockett

Category:

Sprint/Milestone:

Start date:

2016-08-30

Due date:

% Done:

100%

Estimated time:

Applies to JS Branch:

0.9

Fix Committed on JS Branch:

0.9

Fixed in JS Release:

Saxon-JS 0.9.1

SEF Generated with:

Platforms:

Company:

Contact person:

Additional contact persons:

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@.

Actions

Copy link

Updated by Michael Kay over 8 years ago

Thanks, yes, this is a known limitation of the current Saxon-JS beta release.

Actions

Copy link

Updated by Debbie Lockett over 8 years ago

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.

Actions

Copy link

Updated by Debbie Lockett over 8 years ago

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).

Actions

Copy link

Updated by Debbie Lockett about 8 years ago

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.

Actions

Copy link