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 7279 - missing whitespace from expected ValStrict tests.
Summary: missing whitespace from expected ValStrict tests.
Status: RESOLVED FIXED
Alias: None
Product: XQuery Update Facility Test Suite
Classification: Unclassified
Component: XQuery Update Facility Test Suite (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: ---
Assignee: Michael Kay
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-14 20:04 UTC by Markos Zaharioudakis
Modified: 2009-11-05 14:28 UTC (History)
0 users

See Also:


Attachments

Description Markos Zaharioudakis 2009-08-14 20:04:13 UTC
In query valstrict-ins-005-test.xq there are some spaces after the closing tags </c>, </e>, and </f>. These spaces are omitted from the expected result for this test.

The same problem exists in the following tests as well:

valstrict-del-002
valstrict-del-004
valstrict-ins-003
valstrict-ins-005
valstrict-ins-007
valstrict-ren-003
valstrict-repnode-003

and the revalidate-xxx versions of the above.
Comment 1 Michael Kay 2009-11-05 12:23:24 UTC
I'm inclined to see the problem the other way round - see bug #7793. I think there is too much whitespace in the results.

You say: In query valstrict-ins-005-test.xq there are some spaces after the closing tags </c>, </e>, and </f>. These spaces are omitted from the expected result for this test.

But this is boundary whitespace, as defined in section 3.7.1.4 of the XQuery 1.0 spec, and by default boundary whitespace in the query has no significance.

The whitespace in the result comes not from copying the boundary whitespace in the query, but from running the serializer (incorrectly) with indent=yes.

I am proposing to regenerate the results using indent=no, and this will eliminate the whitespace that is currently there.
Comment 2 Michael Kay 2009-11-05 14:28:13 UTC
I have regenerated the results with indent="no" omit-xml-declaration="yes", so
I believe the problem is now fixed, and am closing the bug accordingly.