This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 26728 - [XT30TS] error-1620a, error-1630a
Summary: [XT30TS] error-1620a, error-1630a
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Recommendation
Hardware: PC Windows NT
: P2 normal
Target Milestone: ---
Assignee: Abel Braaksma
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-09-04 16:01 UTC by Tim Mills
Modified: 2015-05-06 21:21 UTC (History)
2 users (show)

See Also:


Attachments

Description Tim Mills 2014-09-04 16:01:15 UTC
These tests expect XTRE1620 and XTRE1630 respectively, but the stylesheets do not use xsl:text or xsl:value-of.  Am I missing something?

<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform" version="3.0"><!--It is a recoverable dynamic error
                     if an xsl:value-of or xsl:text instruction
                     specifies that output escaping is to be disabled when writing to a final result tree that is not being
                     serialized. The optional recovery action is to ignore the
                           disable-output-escaping attribute.
                  -->
   <xsl:template name="main">
      <out>
         <x/>
      </out>
   </xsl:template>
</xsl:stylesheet>
Comment 1 Michael Kay 2014-09-04 17:17:49 UTC
(The skeletons of these tests were auto-generated and there may be a few that haven't yet been populated, especially in the case of tests marked as 2.0-only, or other tests that Saxon can't run for one reason or another).

I've fixed error-1620a.

error-1630a is awaiting a new attribute in the test suite, appearing soon, that says whether the test results should be serialized or not. I'll leave the bug open until we get that in place.
Comment 2 Abel Braaksma 2015-03-30 20:29:51 UTC
This was fixed as a result of working on this to split it up into two tests for 2.0 and 3.0 (error has disappeared) and to allow for recovery, see Bug 23896.

Closing this as solved, the serialize option was introduced and serialize is now off.
Comment 3 Abel Braaksma 2015-05-06 21:21:40 UTC
Was resolved > 30 days ago, closing.