Project

Profile

Help

Bug #5712

open

Secondary result documents in the browser

Added by Debbie Lockett about 2 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
API
Sprint/Milestone:
Start date:
2022-10-06
Due date:
% Done:

0%

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

Description

Currently when running a transform in the browser, it is expected that all secondary result documents produced using xsl:result-document are intended to be added to the HTML page. So in the browser, if the value of xsl:result-document/@href doesn't start with '?' or '#', then an error is always thrown.

The documentation for the deliverResultDocument transform option says that it can be used to supply a handler for secondary result documents, which would replace the usual "html-page" handling, but actually this does not work in the browser. In the resultDoc expression implementation code, in the browser (when !(context.fixed.isDynamicStylesheet)) the destination default is "html-page", and then deliverResultDocument is only used if destination!=="html-page". So attempting to use deliverResultDocument in the browser, just results in FORG0001: xsl:result-document/@href value in browser must be '?.' or '#frag' errors.

We don't currently have any browser unit tests for deliverResultDocument. (Note that Bug #5493: Problems with transform result output.resultDocuments focussed on result documents on the Node.js platform.)

No data to display

Please register to edit this issue

Also available in: Atom PDF Tracking page