- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 08 Oct 2008 20:25:33 +0000
- To: public-qt-comments@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=5849 --- Comment #3 from Michael Kay <mike@saxonica.com> 2008-10-08 20:25:33 --- At its telcon on 2 Oct 2008 the WG agreed in principle that it would be good to fix this so that the answer for the given use case is "1 2 3 4 1 2 3 4". The challenge is to produce a change proposal that will have this effect without having any nasty side-effects on other use cases. The proposed change is in 12.2, under level="any", to change the second bullet so that it uses the expression $S/(preceding::node()|ancestor-or-self::node())[matches-from(.)][last()] in place of $S/(preceding::node()|ancestor::node())[matches-from(.)][last()] Now (a) this only affects level="any" (b) it only affects the numbering of the selected node if it matches the "from" pattern so it seems fairly clear that the change will be fairly limited in scope. It's also the case that both level="single" and level="multiple" use ancestor-or-self() in searching for nodes that match the "from" pattern: that is, they both treat "from" as inclusive, whereas level="any" currently treats "from" as exclusive. So the change improves consistency. So, after sleeping on it, I've convinced myself this is a good change. If the WG agrees, I will validate it further by implementing it and seeing whether it changes the result of any other test cases. -- 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 Wednesday, 8 October 2008 20:26:08 UTC