- From: <bugzilla@jessica.w3.org>
- Date: Wed, 30 Jul 2014 10:16:29 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26468
Bug ID: 26468
Summary: Shadow attributes do not cover the use-case for
optional xsl:use-package
Product: XPath / XQuery / XSLT
Version: Last Call drafts
Hardware: PC
OS: Windows NT
Status: NEW
Severity: normal
Priority: P2
Component: XSLT 3.0
Assignee: mike@saxonica.com
Reporter: abel.braaksma@xs4all.nl
QA Contact: public-qt-comments@w3.org
This bug was originally reported by mail in the WG,
https://lists.w3.org/Archives/Member/w3c-xsl-wg/2014Jul/0055.html (member
only). The relevant part of the mail is this:
Consider:
<xsl:package …>
<xsl:use-package _name="package-$debug.xsl" />
<xsl:stylesheet ...>
<xsl:param name="debug" select=" 'debug' " />
</xsl:stylesheet>
</xsl:package>
The problem lies with the scoping of variables. If you specify a parameter
inside xsl:stylesheet, the scope (the way I understand it) does not extend
beyond the enclosing xsl:stylesheet element (similarly, the param is not
available on the xsl:stylesheet element itself).
We are allowed to move the xsl:use-package below the xsl:stylesheet element
(which solve the tree-traversal order issue of the static param having to
appear before its usage). But I don't think this solves the scoping issue. Any
idea how to solve this, or am I misinterpreting the scoping rules?
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 30 July 2014 10:16:31 UTC