Actions
Bug #4962
open
SEF compiled with Saxon-EE returns system-property('xsl:product-name') as SAXON
Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
2021-04-05
Due date:
% Done:
0%
Estimated time:
Legacy ID:
Applies to branch:
Fix Committed on Branch:
Fixed in Maintenance Release:
Platforms:
Description
I'm printing out <xsl:value-of select="system-property('xsl:product-name')"/>
and getting SAXON
when the stylesheet is compiled with Saxon-EE. I get Saxon-JS
if it's compiled with Saxon-JS. Why the difference if in both cases it executes on Saxon-JS?
Also I don't think the browser-check proposed under XSLT 3.0 and XPath 3.1 Conformance can work with SAXON
then:
<xsl:variable name="inBrowser"
select="system-property('xsl:product-name') eq 'Saxon-JS' and
system-property('saxon:platform') eq 'Browser'"/>
Updated by Norm Tovey-Walsh about 1 year ago
- Project changed from SaxonJS to Saxon
- Applies to JS Branch deleted (
2)
The why is that the Java processor optimizes the call at compile time. This is clearly a bug when compiling a SEF. Moving this issue to the Saxon issue tracker.
Please register to edit this issue
Actions