Project

Profile

Help

Bug #4132

xsl:function does not accept an EQName containing no colon

Added by Michael Kay over 2 years ago. Updated over 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
XSLT conformance
Sprint/Milestone:
-
Start date:
2019-02-12
Due date:
% Done:

100%

Estimated time:
Legacy ID:
Applies to branch:
9.9, trunk
Fix Committed on Branch:
9.9, trunk
Fixed in Maintenance Release:
Platforms:

Description

xsl:function requires the value of the name attribute to contain a colon, even if it is written in the form `name="Q{uri}local". That is, this form of name is only accepted if the URI contains a colon.

Revealed by new test case copy-1220. (Actually, it's difficult to write a good test case, because processors are allowed to reject namespace names that aren't valid absolute URIs, and all valid absolute URIs contain a colon.)

History

#1 Updated by Michael Kay over 2 years ago

  • Status changed from New to Resolved
  • Fix Committed on Branch 9.9, trunk added

Fixed in XSLFunction.prepareAttributes()

#2 Updated by O'Neil Delpratt over 2 years ago

  • Status changed from Resolved to Closed
  • % Done changed from 0 to 100
  • Fixed in Maintenance Release 9.9.1.2 added

Bug issue fixed in the Saxon 9.9.1.2 maintenance release.

Please register to edit this issue

Also available in: Atom PDF