[Bug 3002] [XSLT] xsl:next-match and pattern with |

http://www.w3.org/Bugs/Public/show_bug.cgi?id=3002


mike@saxonica.com changed:

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




------- Comment #3 from mike@saxonica.com  2006-03-24 23:34 -------
The XSL WG considered this at the telcon this week and directed the editor to
add a Note explaining the behavior. This note will be added after the bullet in
6.7 explaining the effect of xsl:next-match, and reads as follows:

<note diff="add" at="ZA">As explained in <specref ref="conflict"/>, a template
rule whose match pattern contains multiple alternatives separated by 
code>|</code> is treated equivalently to a set of template rules, one for each
alternative. This means that where the same node matches more than one 
alternative, and the alternatives have different priority, it is possible for 
the <elcode>next-match</elcode> instruction to cause the current template rule
to be invoked recursively. This situation does not occur when the alternatives
have the same priority.</note>

Received on Friday, 24 March 2006 23:34:17 UTC