- From: <bugzilla@jessica.w3.org>
- Date: Mon, 15 Feb 2016 14:41:02 +0000
- To: public-qt-comments@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29434
Michael Kay <mike@saxonica.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |FIXED
--- Comment #5 from Michael Kay <mike@saxonica.com> ---
We reviewed this and decided there was no need to change the current rules, but
it would be useful to have more examples and explanation as to how xsl:on-empty
and xsl:on-non-empty interact with xsl:attribute (and other instructions that
generate attributes or namespaces); we should also mention the workaround of
using xsl:sequence to specify the scope more precisely, e.g.
<table>
<xsl:attribute..../>
<xsl:sequence>
...
<xsl:on-empty.../>
</xsl:sequence>
</table>
Could also add a Note that zero-length strings don't satisfy this definition of
emptiness.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 15 February 2016 14:41:05 UTC