[Mono-bugs] [Bug 666249] New: XmlElement.AppendChild(XmlDocumentFragment) returns wrong node

[bugzilla_noreply at novell.com]

https://bugzilla.novell.com/show_bug.cgi?id=666249

https://bugzilla.novell.com/show_bug.cgi?id=666249#c0


           Summary: XmlElement.AppendChild(XmlDocumentFragment) returns
                    wrong node
    Classification: Mono
           Product: Mono: Class Libraries
           Version: 2.6.x
          Platform: Macintosh
        OS/Version: Mac OS X 10.6
            Status: NEW
          Severity: Normal
          Priority: P5 - None
         Component: Sys.XML
        AssignedTo: atsushi at ximian.com
        ReportedBy: david.lein at autodesk.com
         QAContact: mono-bugs at lists.ximian.com
          Found By: ---
           Blocker: ---


User-Agent:       Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 5.1;
Trident/4.0; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30; .NET CLR 3.0.04506.648;
NET CLR 3.0.4506.2152; .NET CLR 3.5.30729; OfficeLiveConnector.1.3;
OfficeLivePatch.0.0; .NET4.0C; MS-RTC LM 8)

Consider this code fragment:

XmlDocument doc1 = new XmlDocument();
doc.Load(xmlFile);
XmlDocument doc2 = new XmlDocument();
XmlDocumentFragment docFrag = doc2.CreateDocumentFragment();
docFrag.InnerXml = doc1.OuterXml;
XmlNode node = doc2.DocumentElement.AppendChild(docFrag);

Node should point to the first node in docFrag but instead it is pointing to
the actual fragment element. This is inconsistent with .NET and useless.

Reproducible: Always

Steps to Reproduce:
1. See above.
2.
3.
Actual Results:  
XmlElement.AppendChild(XmlDocumentFragment frag) returns the actual fragment
element.

Expected Results:  
XmlElement.AppendChild(XmlDocumentFragment frag) should return the first node
that has been appended.

-- 
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.