Bug #5749
closedresolve-uri issue base-uri with a fragment
0%
Description
SaxonJS 2.5 introduced a bug with resolve-uri() and base-uri(), when the base-uri includes a fragment.
A reproduction of this issue is deployed here:
https://blog.crushingpennies.com/saxon-js-fragment-bug/
With the corresponding source code here: https://github.com/danielnaab/saxon-js-fragment-bug
You will note that SaxonJS.transform() is invoked with a sourceNode rather than specified by URL. As a result, base-uri falls back to the browser's current URL. Secondly, when that URL includes a fragment, errors of this form are returned:
http://localhost:3000/saxon-js-2.5#fragment contains a fragment identifier; code:FORG0002
Also note that the reproduction confirms that this behavior did not exist in SaxonJS 2.4.
Please register to edit this issue
Also available in: Atom PDF Tracking page