W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2011

Re: [XHR] responseType "json"

From: Olli Pettay <Olli.Pettay@helsinki.fi>
Date: Mon, 12 Dec 2011 15:37:04 +0200
Message-ID: <4EE60380.1080503@helsinki.fi>
To: Jarred Nicholls <jarred@sencha.com>
CC: Anne van Kesteren <annevk@opera.com>, public-webapps@w3.org
On 12/12/2011 03:12 PM, Jarred Nicholls wrote:
> On Mon, Dec 12, 2011 at 5:37 AM, Anne van Kesteren <annevk@opera.com
> <mailto:annevk@opera.com>> wrote:
>
>     On Sun, 11 Dec 2011 15:44:58 +0100, Jarred Nicholls
>     <jarred@sencha.com <mailto:jarred@sencha.com>> wrote:
>
>         I understand that's how you spec'ed it, but it's not how it's
>         implemented
>         in IE nor WebKit for legacy purposes - which is what I meant in
>         the above
>         statement.
>
>
>     What do you mean legacy purposes? responseType is a new feature. And
>     we added it in this way in part because of feedback from the WebKit
>     community that did not want to keep the raw data around.
>
>
> I wasn't talking about responseType, I was referring to the pair of
> responseText and responseXML being accessible together since the dawn of
> time.

In case responseType is not set. If responseType is set, implementations
can optimize certain things.

>  I don't know why WebKit and IE didn't take the opportunity to use
> responseType
responseType is a new thing. Gecko hasn't changed behavior in case
responseType is not set.

> and kill that behavior; don't ask me, I wasn't responsible
> for it ;)
>
>
>     In the thread where we discussed adding it the person working on it
>     for WebKit did seem to plan on implementing it per the specification:
>
>     http://lists.w3.org/Archives/__Public/public-webapps/__2010OctDec/thread.html#msg799
>     <http://lists.w3.org/Archives/Public/public-webapps/2010OctDec/thread.html#msg799>
>
>
> Clearly not - shame, because now I'm trying to clean up the mess.
>
>
>
>
>         In WebKit and IE <=9, a responseType of "", "text",
>         or "document" means access to both responseXML and responseText.
>           I don't
>         know what IE10's behavior is yet.
>
>
>     IE8 could not have supported this feature and for IE9 I could not
>     find any documentation. Are you sure they implemented it?
>
>
> I'm not positive if they did to be honest - I haven't found it
> documented anywhere.
>
>
>
>     Given that Gecko does the right thing and Opera will too (next major
>     release I believe) I do not really see any reason to change the
>     specification.
>
>
> I started an initiative to bring XHR in WebKit up-to-spec (see
> https://bugs.webkit.org/show_bug.cgi?id=54162) and got a lot of push
> back.  All I'm asking is that if I run into push back again, that I can
> send them your way ;)
>
>
>
>
>     --
>     Anne van Kesteren
>     http://annevankesteren.nl/
>
>
>
>
> --
> ................................................................
>
> *Sencha*
> Jarred Nicholls, Senior Software Architect
> @jarrednicholls
> <http://twitter.com/jarrednicholls>
>
Received on Monday, 12 December 2011 13:38:21 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:49 GMT