20022 – [XT3TS] Tests using xsl:output with assert-xml

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 20022 - [XT3TS] Tests using xsl:output with assert-xml

Summary: [XT3TS] Tests using xsl:output with assert-xml

Status:	CLOSED FIXED

Alias:	None

Product:	XPath / XQuery / XSLT
Classification:	Unclassified
Component:	XSLT 3.0 Test Suite (show other bugs)
Version:	Working drafts
Hardware:	PC Windows 3.1

Importance:	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:	2012-11-20 15:33 UTC by Tim Mills
Modified:	2012-12-13 10:52 UTC (History)
CC List:	1 user (show)

See Also:

Attachments

Description Tim Mills 2012-11-20 15:33:34 UTC

The assertion assert-xml tests the pre-serialized output of the transformation.

Some tests which use <xsl:output indent="yes" /> use assert-xml with expected results containing indentation.  Since the indentation is significant with respect to canonicalization, the indentation should not appear in the expected result.

This bug report is filed to record such problems.

regex-007

Comment 1 Michael Kay 2012-11-21 16:31:37 UTC

I have added test catalog-004 which reports a list of stylesheets that use indent="yes" and test the results using assert-xml. It's a long list (so the test currently fails). I'm doing a second pass over the test sets and will fix the problems as I come to them.

I've fixed the regex testset today.

Comment 2 Tim Mills 2012-11-29 10:18:56 UTC

predicate-031 has this problem.  I will commit a fix.

Comment 3 Michael Kay 2012-12-11 22:14:21 UTC

I've fixed all the tests that were identified by the catalog check in catalog-004, so I'm marking this resolved.

Comment 4 Tim Mills 2012-12-13 10:52:43 UTC

Confirmed fixed.  Thanks.

There may be some cases not picked up by catalog-004.  e.g. where there's no xsl:output/@indent but the xsl:output/@method is (x)html, or where there's no xsl:output/@mode and the stylesheet happens to generate HTML.