[Bug 27014] New: [xslt 3.0] xsl:context-item as="..." use="prohibited"

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

[Bug 27014] New: [xslt 3.0] xsl:context-item as="..." use="prohibited"

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

            Bug ID: 27014
           Summary: [xslt 3.0] xsl:context-item as="..." use="prohibited"
           Product: XPath / XQuery / XSLT
           Version: Working drafts
          Hardware: PC
                OS: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: XSLT 3.0
          Assignee: [hidden email]
          Reporter: [hidden email]
        QA Contact: [hidden email]

It should surely be a static error to specify the "as" attribute on
xsl:context-item when use="prohibited" is specified - it doesn't make sense to
say what the type of the context item must be, and then say it must be absent.

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

Reply | Threaded
Open this post in threaded view
|

[Bug 27014] [xslt 3.0] xsl:context-item as="..." use="prohibited"

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

--- Comment #1 from Michael Kay <[hidden email]> ---
Applies equally to xsl:global-context-item

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

Reply | Threaded
Open this post in threaded view
|

[Bug 27014] [xslt 3.0] xsl:context-item as="..." use="prohibited"

Bugzilla from bugzilla@jessica.w3.org
In reply to this post by Bugzilla from bugzilla@jessica.w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27014

Michael Kay <[hidden email]> changed:

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

--- Comment #2 from Michael Kay <[hidden email]> ---
The WG agreed to make it an error if use="prohibited" and exists(@as).

The change has been made.

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