W3C home > Mailing lists > Public > public-qt-comments@w3.org > October 2008

[Bug 5849] [XSLT 2.0] xsl:number problem

From: <bugzilla@wiggum.w3.org>
Date: Fri, 10 Oct 2008 10:21:30 +0000
To: public-qt-comments@w3.org
Message-Id: <E1KoF7i-0002al-NR@farnsworth.w3.org>


--- Comment #4 from Michael Kay <mike@saxonica.com>  2008-10-10 10:21:30 ---
I have experimentally implemented the change in comment #3 to review the effect
on the test suite.

It affects the result of three xsl:number tests: numb41, numb44, and numb45.

numb45 is the test case described in the bug report, and it now produces the
numbering (1,2,3,4,1,2,3,4)

numb44 is a rather artificial test designed to exercise the use of current() in
a predicate: <xsl:number from="*[name()=name(current())]/*" level="any"/>. The
effect of the change is that a node that matches the "from" pattern (that is, a
node that has the same name as its parent) is now numbered 1; previously it was
numbered based on its distance from the previous node that had the same name as
its parent.

numb41 tests numbering of attribute nodes: <xsl:number level="any"
count="node() | / | @*" from="@*"/>. Previously when this was applied to an
attribute node, there would be no ancestor or descendant that matched the
"from" pattern, so no number was allocated (blank output). Now the attribute
node itself matches the "from" pattern, so it is given the number 1.

So it seems that the change has no unwanted side-effects: the only change is
for level="any", when there is a from pattern and the numbered node matches the
from pattern, it is now numbered 1.

Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Friday, 10 October 2008 10:22:06 UTC

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