Project

Profile

Help

Bug #4641

closed

xpath-default-namespace not being honoured on ixsl:*/@object

Added by John Lumley over 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Low
Category:
-
Sprint/Milestone:
-
Start date:
2020-07-13
Due date:
% Done:

100%

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

Description

I've had a couple of cases where the XPath expression in the object attribute of ixsl instructions needs specific namespace bindings (i.e adding a prefix) rather than defaulting to the xpath-default-namespace in scope, using the XX compiler. Will investigate.

Actions #1

Updated by Debbie Lockett about 4 years ago

  • Applies to JS Branch 2.0 added

JS2 unit tests ixsl/setStyle20 and setStyle21 added.

e.g. setStyle21 does:

    <xsl:template name="main" xpath-default-namespace="http://www.w3.org/2000/svg">
        <ixsl:set-style name="display" select="'none'"
            object="ixsl:page()/html:html/html:body//svg"/>
    </xsl:template>

Which should hide the SVG element in the HTML page, but these fail with XX SEFs.

Actions #2

Updated by Community Admin almost 4 years ago

  • Applies to JS Branch 2 added
  • Applies to JS Branch deleted (2.0)
Actions #3

Updated by Debbie Lockett over 3 years ago

  • Status changed from New to Resolved
  • Assignee changed from John Lumley to Debbie Lockett
  • Fix Committed on JS Branch 2 added

JS unit tests ixsl/setStyle20 and setStyle21 ported over to new Selenium testing framework (mochaBrowserTests).

Code fix committed in XX compiler in ixsl.xsl, to ensure that xpath-default-namespace is included on IXSL extension instructions when relevant.

Actions #7

Updated by Norm Tovey-Walsh over 3 years ago

  • Status changed from Resolved to Closed

This issue has been resolved in the Saxon 2.2 maintenance release.

Actions #8

Updated by Debbie Lockett over 3 years ago

  • % Done changed from 0 to 100
  • Fixed in JS Release set to Saxon-JS 2.2

Please register to edit this issue

Also available in: Atom PDF Tracking page