https://bugzilla.novell.com/show_bug.cgi?id=681835
https://bugzilla.novell.com/show_bug.cgi?id=681835#c2 Atsushi Enomoto <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |RESOLVED Resolution| |FIXED --- Comment #2 from Atsushi Enomoto <[email protected]> 2011-03-23 12:29:49 UTC --- It was a difficult issue to fix, but now it's working in git master (9955d9e). >From the commit message ---------- ContentProperty with collection caused unexpected read in XamlXmlReader. The fix is actually complicated. When a ContentProperty list is settable, NET allows omitting start element for it i.e. it *may* or *may not* appear, which for each is interpreted as: - it is StartObject if the start element can be of the member. - otherwise it is GetObject. It could still happen that if such a list could contain an instance of the same list type, which results in "indeterminant" state. I don't think MS XAML syntax and/or parser is carefully designed to treat such situation gracefully, so I leave current implementation as is. ---------- -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug. _______________________________________________ mono-bugs maillist - [email protected] http://lists.ximian.com/mailman/listinfo/mono-bugs
