[Bug 29210] [xslt30] xsl:apply-imports and xsl:next-match from within xsl:override

https://www.w3.org/Bugs/Public/show_bug.cgi?id=29210

Michael Kay <mike@saxonica.com> changed:

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

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
After discussion, the WG decided to go with the option that xsl:apply-imports
is permitted, and is effectively a no-op (because the set of candidate template
rules to consider is inevitably empty).

The effect is to delete the paragraph

[ERR XTSE3460] It is a static error if an xsl:apply-imports element appears in
a template rule declared within an xsl:override element. (To invoke the
template rule that is being overridden, xsl:next-match should therefore be
used.)

and replace it with a note:

Note: If xsl:apply-imports is evaluated when the current template rule is
declared within an xsl:override element, the set of candidate template rules
will always be empty. This is because template rules for the relevant mode
cannot be declared anywhere in the using package other than within the
xsl:override element itself. 

The problems in (B) and (C) will also be fixed.

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

Received on Thursday, 22 October 2015 20:20:00 UTC