W3C home > Mailing lists > Public > public-qt-comments@w3.org > February 2016

[Bug 29455] [xslt30ts] on-empty-113a

From: <bugzilla@jessica.w3.org>
Date: Wed, 17 Feb 2016 10:32:53 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29455-523-PqIOEtZhDl@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29455

--- Comment #4 from Michael Kay <mike@saxonica.com> ---
Studying the effect on this example:

        <xsl:for-each select="1 to 100">
            <xsl:sequence select="''" />
            <xsl:on-empty select="'|'" />
        </xsl:for-each>

we realised that if the conditions are right for on-empty to fire (which, under
the new rules, is the case here), then the content produced by on-empty must be
output *instead of* the result of the SC, not *in addition to* that result. So
some buffering is necessary, but only of tiny amounts of data.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 17 February 2016 10:32:57 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:59 UTC