[Bug 26800] New: [XT30] evaluate-007, fn:current is not allowed in xsl:evaluate

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

[Bug 26800] New: [XT30] evaluate-007, fn:current is not allowed in xsl:evaluate

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26800

            Bug ID: 26800
           Summary: [XT30] evaluate-007, fn:current is not allowed in
                    xsl:evaluate
           Product: XPath / XQuery / XSLT
           Version: Last Call drafts
          Hardware: PC
                OS: Windows NT
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0 Test Suite
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

As in the title. The test tests fn:current inside xsl:evaluate, but per the
section on the static context, that function is not allowed in dynamic
evaluations:

<quote>
Function signatures: All core functions; constructor functions for named simple
types included in the in-scope schema definitions; all user-defined functions
and accumulator functions present in the containing package provided their
visibility is not hidden or private; and an implementation-defined set of
extension functions.

Note that this set deliberately excludes XSLT-defined functions in the standard
function namespace including for example, key, current-group, and
system-property A list of these functions is in G List of XSLT-defined
functions.
</quote>

--
You are receiving this mail because:
You are the QA Contact for the bug.

Reply | Threaded
Open this post in threaded view
|

[Bug 26800] [XT30] evaluate-007, fn:current is not allowed in xsl:evaluate

Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26800

Abel Braaksma <[hidden email]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|---                         |FIXED

--- Comment #1 from Abel Braaksma <[hidden email]> ---
Fixed in Rev#680 and Rev#682.

--
You are receiving this mail because:
You are the QA Contact for the bug.