Support #5679
closed
SaxonJS and the documentPool
0%
Description
This bug tracks an issue raised initially on the XML.com Slack. (This gives it a bug number for my local test case, more than anything else.)
Updated by Norm Tovey-Walsh over 1 year ago
Everytime you run a transformation, any event handlers in the stylesheet get instantiated. If you run the same stylesheet more than once, then they get instantiated more than once.
The behavior seen with the documentPool is red herring. The first transformation, the one with the document pool established on it, always succeeds. The apparent failure arises because event handlers instantiated in subsequent uses of that stylesheet, without establishing a document pool, also run and they fail.
It's not clear that there's anything unexpected going on here.
Updated by Norm Tovey-Walsh over 1 year ago
- Status changed from New to Resolved
Added a test case to demonstrate that setting the nonInteractive option to true prevents the event handlers from being re-applied.
(No code changes were required to resolve this issue.)
Updated by Debbie Lockett over 1 year ago
- Tracker changed from Bug to Support
- Status changed from Resolved to Closed
Please register to edit this issue
Also available in: Atom PDF Tracking page
.