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 Note at the bottom of 8.3 Try/catch is not entirely true anymore since the introduction of the rollback-output attribute. The current Note is: <quote> If an error occurs while evaluating an instruction within xsl:try, then no instruction within the xsl:try has any effect on the result returned by the xsl:try instruction. This means that if a processor is streaming the output to a serializer, it needs to adopt a strategy such as buffering the output in memory so that nothing is written until successful completion of the xsl:try instruction, or checkpointing the output so it can be rolled back when an error occurs. </quote> My proposal would be to extend the note with something along those lines: <proposal> [...] so it can be rolled back when an error occurs, unless the setting for rollback-output is set to no, as explained in the next section. </proposal>
I'm going to simply delete the Note. The same information is provided in much greater detail in the immediately following section.