[Mono-bugs] [Bug 80652][Nor] New - XmlTextWriter output/node indent level errors

bugzilla-daemon at bugzilla.ximian.com bugzilla-daemon at bugzilla.ximian.com
Sun Jan 28 21:11:25 EST 2007

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 mjscod at gmx.de.


--- shadow/80652	2007-01-28 21:11:25.000000000 -0500
+++ shadow/80652.tmp.17558	2007-01-28 21:11:25.000000000 -0500
@@ -0,0 +1,57 @@
+Bug#: 80652
+Product: Mono: Class Libraries
+Version: 1.2
+OS Details: Ubuntu Feisty Fawn AMD64
+Status: NEW   
+Priority: Normal
+Component: Sys.XML
+AssignedTo: atsushi at ximian.com                            
+ReportedBy: mjscod at gmx.de               
+QAContact: mono-bugs at ximian.com
+TargetMilestone: ---
+Summary: XmlTextWriter output/node indent level errors
+Please fill in this template when reporting a bug, unless you know what you
+are doing.
+Description of Problem:
+Mono's XmlTextWriter produces wrong output and/or fails with errors where
+it shouldn't. The problem is that many test cases of the SgmlReader simply
+fail because of suppressed empty lines, buggy attribute node handling,
+spurious inserted line breaks and probably messed up implicit closing of nodes.
+Steps to reproduce the problem:
+1. Download SgmlReader from GotDotNet:
+2. Compile the solution with VS2003 or VS2005
+3. Execute the test application with Mono
+Actual Results:
+Many failing tests due to the following reasons:
+1. Line endings (understandable and not a problem at all)
+2. Suppressed empty lines at the beginning of a document
+3. Suppressed empty lines at the end of a document
+4. Forgotten attribute nodes
+5. Superfluous line breaks ("<html
+6. Messed up implicit closing of nodes? Not sure about this one but the
+test failed with an InvalidOperationException ("no more open element").
+Expected Results:
+All tests should pass when the line endings of the resources and test
+documents were converted from CR/LF to LF.
+How often does this happen? 
+Additional Information:
+The problems 4 and 6 may be major but the other ones are minor (IMHO) but
+they should be fixed too because there might be applications that may rely
+on this behavior.

More information about the mono-bugs mailing list