- From: <bugzilla@wiggum.w3.org>
- Date: Fri, 07 Jul 2006 00:12:11 +0000
- To: public-qt-comments@w3.org
- CC:
http://www.w3.org/Bugs/Public/show_bug.cgi?id=3419
joaquin.delgado@oracle.com changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution| |FIXED
------- Comment #1 from joaquin.delgado@oracle.com 2006-07-07 00:12 -------
This standalone UnaryNot does not have a bug.
The negation of an empty <allMatches> is not an empty <allMatches> but an
<allMatches> with one empty <match>. That is clear in the definition of
fts:UnaryNotHelper. It populates <match/> when there is no <match> in
<allMatches>. This empty <match> element satisfies fts:FTContainsExpr because
it has no <stringExclude>. So, ftcontains returns TRUE as expected.
Thanks,
J.D.
Received on Friday, 7 July 2006 00:12:13 UTC