- From: SULLIVAN, BRYAN L (ATTCINW) <BS3131@att.com>
- Date: Mon, 9 Aug 2010 14:37:25 -0700
- To: "Anne van Kesteren" <annevk@opera.com>, "Jonas Sicking" <jonas@sicking.cc>
- Cc: "WebApps WG" <public-webapps@w3.org>
Anne, Are you saying that it should not be possible now (with XHR L1) to receive HTML files via XHR ("Receiving HTML documents would indeed be a newish feature ") ? This does actually work for me in XHR L1, so I'm unclear about what you mean below. Thanks, Bryan Sullivan | AT&T -----Original Message----- From: public-webapps-request@w3.org [mailto:public-webapps-request@w3.org] On Behalf Of Anne van Kesteren Sent: Monday, August 09, 2010 1:25 PM To: Jonas Sicking Cc: WebApps WG Subject: Re: [XHR] Status Update On Mon, 09 Aug 2010 20:54:48 +0200, Jonas Sicking <jonas@sicking.cc> wrote: > Some of these bugs are feature enhancements. Such as adding support > for sending and receiving text/html documents. In the interest of > getting us to rec as quickly as possible I suggest that these features > are added to XHR L2 instead. Actually, by virtue of following the Document.innerHTML algorithm from HTML5 sending HTML documents is already covered for in XMLHttpRequest. It is just that the media type (as the bug indicates) is always set to application/xml rather than text/html for HTML documents. Receiving HTML documents would indeed be a newish feature, except that you already need to follow HTML5 rules to discover the character encoding for responseText, etc. so adding this did not seem like a big burden on implementations on top of which it makes sense that if you can send them (which was already possible) you can also receive them. You say "such as" but I believe these are the only two bugs that can be classified as such and the former is really a bug and not a new feature. -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 9 August 2010 21:38:01 UTC