Project

Profile

Help

Actions
Send by e-mail Copy link

Bug #5749

closed

resolve-uri issue base-uri with a fragment

Added by Daniel Naab over 1 year ago. Updated over 1 year ago.

Status:
Won't fix
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2022-11-29
Due date:
% Done:

0%

Estimated time:
Applies to JS Branch:
Fix Committed on JS Branch:
Fixed in JS Release:
SEF Generated with:
Platforms:
Company:
-
Contact person:
-
Additional contact persons:
-

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

Actions
Send by e-mail Copy link

Also available in: Atom PDF Tracking page