[Bug 24378] [XSLT30] xsl:on-empty on more instructions


Michael Kay <mike@saxonica.com> changed:

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

--- Comment #2 from Michael Kay <mike@saxonica.com> ---
On 24 July 2014 the WG decided that the [xsl:]on-empty attribute should apply
only to literal result elements, xsl:element, and xsl:copy, and that in the
case of xsl:copy it should apply only when the node being copied is an element

The reasons for this are that (a) the major use cases for on-empty are
concerned with construction of element nodes; (b) the concept of "emptiness"
for elements and for nodes such as attributes is quite different, and
overloading the concept gets messy, especially in the case of xsl:copy where
the different meanings are mixed in one instruction.

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

Received on Sunday, 27 July 2014 19:07:57 UTC