This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
The tests in strm/si-try are written in the mistaken belief that the specification allows try/catch to be streamable. The current (Dec 2013) spec does not.
The current draft says, about xsl:try: "If the select expression and/or sequence constructor of the xsl:catch element are motionless, then the sweep of the select expression and/or sequence constructor of the xsl:try element (whichever is present);" In other words, if <xsl:catch select="motionlessexpr" />, then the body of the xsl:try is streamable, otherwise it is ree-ranging. Going over the tests it seems that all tests are written with xsl:catch having a grounded and motionless expression, meaning that the streamability of the xsl:try body applies. From what I glanced over, it looks like they are written correctly. I'm not sure where in the spec it should say that this is non-streamable.
Meanwhile, the try/catch and its streamability features have received quite some discussion in the working group and many changes have been applied to the spec to accommodate streamable try/catch using the new @rollback-output attribute (see https://www.w3.org/XML/Group/qtspecs/specifications/xslt-30/html/Overview.html#recovery, members only). I will move forward and close this bug report, it seems to have been taken over by events, but feel free to reopen if I'm mistaken.
Was resolved > 30 days ago, closing.