On Tue, 17 Jun 2008 10:29:12 +0200, Zhenbin Xu <[EMAIL PROTECTED]>
wrote:
Technically because all other XHR methods/properties throw exceptions
in case of state violation, exception for responseXML/responseText is
better.
The reason these don't throw an exception anymore is actually documented
on the public-webapi mailing list. Nobody else provided additional
information at the time:
http://lists.w3.org/Archives/Public/public-webapi/2008Feb/thread.html#msg94
Regarding parseError, since the parseError object is not part of DOM Core
and nobody but Internet Explorer supported it, it's not part of
XMLHttpRequest. If we change DOM Core to say that documents with a
namespace well-formedness violation are represented by an empty Document
object with an associated parseError object I suppose we could update
XMLHttpRequest to that effect.
I don't really feel strongly either way though it's a bit unfortunate that
Microsoft comes with this feedback now given that it's been stable this
way since the first W3C XMLHttpRequest draft published over two years ago.
(Returning null for documents that have a namespace well-formedness
violation.)
--
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
