W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: XMLHttpRequest.responseXML and invalid XML documents

From: Hallvord R. M. Steen <hallvord@opera.com>
Date: Mon, 24 Apr 2006 21:48:35 +0200
To: "Anne van Kesteren" <annevk@opera.com>, "Boris Zbarsky" <bzbarsky@mit.edu>
Cc: public-webapi@w3.org
Message-ID: <op.s8i2m9vja3v5gv@id-c0418.oslo.opera.com>

On Mon, 24 Apr 2006 11:09:42 +0200, Anne van Kesteren <annevk@opera.com>  
wrote:

>>> All major browsers return an empty document instead under most of
>>> these conditions.
>
> There's an open <ednote> on this. Basically people might do:
>
>    .responseXML.getElementsByTagName()
>
> ... of course, that would fail in cases where the document is sent as  
> text/html and probably others...

I'm worried that content will break with code like the above if we extend  
the scenarios where returning null is mandatory.

>> Gecko doesn't ever return an empty document from XMLHttpRequest.   
>> Sometimes it returns a bogus document with some "parseerror" markup in  
>> it due to <https://bugzilla.mozilla.org/show_bug.cgi?id=289714>; that's  
>> a bug that needs to be fixed. [...]

OK, thanks for explaining.

-- 
Hallvord R. M. Steen
Core QA JavaScript tester, Opera Software
http://www.opera.com/
Opera - simply the best Internet experience
Received on Monday, 24 April 2006 19:46:52 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:55 GMT