- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Feb 2016 09:59:36 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29455
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|XSLT 3.0 Test Suite |XSLT 3.0
Assignee|abel.online@xs4all.nl |mike@saxonica.com
--- Comment #2 from Michael Kay <mike@saxonica.com> ---
We decided to change this to a spec bug.
We think it is desirable that the rules for xsl:on-empty and xsl:on-non-empty
should be consistent with the rules for constructing complex content (and this
design intent is already indicated by a Note in the spec). Specifically:
Consider the sequence constructor after removing any xsl:on-[non]-empty
instructions. Apply the rules for constructing complex content, ignoring any
error conditions. If the result is empty content, then on-empty fires (and if
not, then on-non-empty fires).
The practical difference from the current rules is that some additional
constructs are considered empty - for example, a zero-length string (but not if
there are adjacent zero-length strings which would cause separators to be
inserted).
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 17 February 2016 09:59:43 UTC