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:16:59 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-29455-523-nC11RIBMIY@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=29455

--- Comment #3 from Michael Kay <mike@saxonica.com> ---
Slight problem: consider

<xsl:sequence>
  <xsl:sequence select="''"/>
  <xsl:on-non-empty select="'NOT EMPTY'"/>
  <xsl:sequence select="''"/>
</xsl:sequence>

Here we don't know whether on-non-empty fires until we know what comes next -
this breaks the current algorithm which is designed to ensure streamability.

We think this can probably be solved by breaking the sequence constructor into
parts at <xsl:on-non-empty/> boundaries, and applying the CCC rules to each of
the parts.

ACTION on the editor to propose spec wording that implements this idea.

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

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