[Mono-bugs] [Bug 333137] XmlTextWriter: WriteAttributeString should result in IOE when WriteState is not Element
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Thu Oct 11 16:33:11 EDT 2007
https://bugzilla.novell.com/show_bug.cgi?id=333137#c2
Atsushi Enomoto <atsushi at ximian.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Severity|Normal |Minor
Priority|P5 - None |P4 - Low
--- Comment #2 from Atsushi Enomoto <atsushi at ximian.com> 2007-10-11 14:33:10 MST ---
There are couple of points that we should not follow .NET behavior:
- The fact that XmlTextWriter used to throw
InvalidOperationException is nothing more than lucky, and
it is not for the same reason as .NET throws. .NET thinks
attribute after attribute is invalid, while mono used to
raise an error since StartAttribute at Attribute state is
wrong.
- Current .NET behavior is of contradiction. It should reject
element (WriteStartElement) too because it also results in
invalid XML output.
I don't want to make such a compatibility change that is very likely changed in
the near future. Making compatibility change that will result in
incompatibility does not make sense. Also such a difference is nothing
practical.
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the mono-bugs
mailing list