W3C home > Mailing lists > Public > public-qt-comments@w3.org > November 2012

[Bug 20016] [XT3TS] accessor-011

From: <bugzilla@jessica.w3.org>
Date: Tue, 20 Nov 2012 11:39:06 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-20016-523-vHbn089n8X@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=20016

Michael Kay <mike@saxonica.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mike@saxonica.com

--- Comment #1 from Michael Kay <mike@saxonica.com> ---
I've removed the final newline.

However, I don't think it was wrong. This test uses assert-xml, which is
defined like this:

The assertion is true if the result of parsing and canonicalizing the XML given
in the body of the assert-xml element is the same (byte-for-byte) as the result
of canonicalizing the XML result of the query. As an alternative to
canonicalizing, the results may be compared using the fn:deep-equal() function.

Under that definition, the trailing newline should not matter. Admittedly, it
becomes a problem when we are comparing XML fragments, but I think that is
quite rare and we should probably label those cases specially.

There are actually quite a few tests where you will need to be tolerant of
whitespace differences. I'm trying to remove them, but it will take time. I
would suggest first doing a comparison as in the spec, and if that fails,
attempting a second comparison after stripping whitespace text nodes from both
the actual and expected results.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 20 November 2012 11:39:13 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:40 UTC