W3C home > Mailing lists > Public > public-webapi@w3.org > February 2007

Re: XHR: responseText encoding detection

From: Anne van Kesteren <annevk@opera.com>
Date: Wed, 28 Feb 2007 17:33:39 +0100
To: "Alexey Proskuryakov" <ap-carbon@rambler.ru>, public-webapi@w3.org
Message-ID: <op.togwadw364w2qv@id-c0020.driveway.uu.nl>

On Wed, 28 Feb 2007 15:43:25 +0100, Alexey Proskuryakov  
<ap-carbon@rambler.ru> wrote:
> Another consideration: architecturally, it may be unwise to combine both  
> loading and parsing functionality in a single API.

Agreed, but that's how it is.


> For XML parsing, DOM3 Load (or another dedicated API) could provide much  
> more control. Obviously, we cannot remove responseXML from  
> XMLHttpRequest, but not adding more known formats sounds like a good  
> idea to me.

Is such control really needed? For most people having responseXML seems  
fine. Given how widely used HTML is it makes sense to make responseXML  
also work for text/html resources given that browsers treat text/html as  
prescribed by HTML5.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Wednesday, 28 February 2007 16:47:02 GMT

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