[Mono-bugs] [Bug 39079][Min] Changed - Reverse axes XPath selection results in nodes in reverse order

bugzilla-daemon@bugzilla.ximian.com bugzilla-daemon@bugzilla.ximian.com
Tue, 4 Nov 2003 13:46:32 -0500 (EST)

Please do not reply to this email- if you want to comment on the bug, go to the
URL shown below and enter your comments there.

Changed by ginga@kit.hi-ho.ne.jp.


--- shadow/39079	2003-03-04 21:24:23.000000000 -0500
+++ shadow/39079.tmp.23324	2003-11-04 13:46:32.000000000 -0500
@@ -1,23 +1,23 @@
 Bug#: 39079
 Product: Mono/Class Libraries
 Version: unspecified
+OS: unknown
 OS Details: 
-Status: NEW   
-Priority: Wishlist
+Status: RESOLVED   
+Resolution: FIXED
+Severity: Unknown
+Priority: Minor
 Component: System.XML
 AssignedTo: mono-bugs@ximian.com                            
 ReportedBy: ginga@kit.hi-ho.ne.jp               
 QAContact: mono-bugs@ximian.com
 TargetMilestone: ---
-Summary: SelectSingleNode 
+Summary: Reverse axes XPath selection results in nodes in reverse order
 Description of Problem:
 Even though we specify xpath reverse order axis expression (e.g.
 "ancestor::foo") MS.NET always returns SelectSingleNode() result
 in document order, non-conformant to W3C XPath recommendation.
@@ -52,6 +52,9 @@
 See "document reverse order" here:
 You may also be intersted in what they say about it:
+------- Additional Comments From ginga@kit.hi-ho.ne.jp  2003-11-04 13:46 -------
+This should be fixed in cvs.