- From: <bugzilla@jessica.w3.org>
- Date: Thu, 28 Nov 2013 22:54:56 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23631
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I have added text that attempts to decide these questions. Generally the XSLT
dynamic context components are cleared by a dynamic function call, so you are
allowed to do function-lookup("regex-group",1), for example, and the result of
calling the resulting function item is as if the context is empty. The same
applies to dynamic calls on fn:current and fn:key. For system-property,
function-available, element-available, and system-property I've added notes
suggesting what they should do, but in the end it's a bit system-dependent.
In all cases, function items returned by XPath expressions such as current#0
and function-lookup() are NOT required to retain the XSLT parts of the
static/dynamic context in their closure.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Thursday, 28 November 2013 22:54:58 UTC