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 27066 - [XT30] Test Include0101 expects incorrect import order
Summary: [XT30] Test Include0101 expects incorrect import order
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 3.0 Test Suite (show other bugs)
Version: Last Call drafts
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-10-15 21:44 UTC by Abel Braaksma
Modified: 2015-05-06 21:17 UTC (History)
1 user (show)

See Also:


Attachments

Description Abel Braaksma 2014-10-15 21:44:45 UTC
In test include-0101, the file include-0101.xsl contains an xsl:import and then an xsl:include. The xsl:import imports a file with <xsl:output method="xml" /> and the xsl:include includes a file with <xsl:output method="html" />.

Since the included file has higher import precedence (it sits at the highest stylesheet module level), the output method to be expected is "html".

Currently, the expected output is:
<body changed="8 Feb 2002" var="E">Text of one-tagText of two-tag<br/></body>

This is either XML or XHTML output, but not HTML output (which should have "<br>" instead).
Comment 1 Michael Kay 2014-10-15 21:59:56 UTC
The test uses assert-xml, which is defined as a comparison of the result tree, not of its serialized form.

<p> Asserts the result of the query by providing a serialization of the
 expression result using the default serialization parameters method="xml"
 indent="no" omit-xml-declaration="yes".</p>

The serialization parameters in the stylesheet have no bearing on the results of assertions other than, e.g. assert-serialization-matches.
Comment 2 Abel Braaksma 2014-10-16 15:01:15 UTC
Oh, ok, in that case, I think I should change the assertion to assert the actual serialization, because otherwise, we cannot assess the part of the test that checks the xsl:output import precedence rules.
Comment 3 Michael Kay 2015-03-20 15:24:49 UTC
According to the test metadata, this was fixed on 2014-11-14
Comment 4 Abel Braaksma 2015-05-06 21:17:16 UTC
Was resolved > 30 days ago, closing.