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

Re: XHR responseArrayBuffer attribute: suggestion to replace "asBlob" with "responseType"

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 3 Nov 2010 12:06:55 +0100
Message-ID: <AANLkTi=mbSXPSqM-cFQPavUZABT8aLghbKPW130E9N-c@mail.gmail.com>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Maciej Stachowiak <mjs@apple.com>, Geoffrey Garen <ggaren@apple.com>, Darin Fisher <darin@chromium.org>, Chris Rogers <crogers@google.com>, Web Applications Working Group WG <public-webapps@w3.org>, Anne van Kesteren <annevk@opera.com>, Eric Uhrhane <ericu@google.com>, michaeln@google.com, Alexey Proskuryakov <ap@webkit.org>, Chris Marrin <cmarrin@apple.com>, jorlow@google.com, jamesr@chromium.org
On Wed, Nov 3, 2010 at 5:16 AM, Boris Zbarsky <bzbarsky@mit.edu> wrote:
> On 11/2/10 11:35 PM, Jonas Sicking wrote:
>>
>> So your concern is that jQuery will update to use the new API before
>> browsers implement it. And then once browsers do implement it and
>> start honoring the .responseType by making various existing properties
>> throw, things will fail?
>
> No, my concern is that browsers will implement this, and then sites that
> haven't updated their jquery, and probably never plan to do it, will start
> using the new stuff browsers have implemented.

But won't that always fail? If the author either sets .responseType
when jquery doesn't expect it, or the author uses .response when
jquery hasn't set .responseType?

Yes, it means that pages that use old code can't use the new features
together with that code, but I don't see that as a big problem in this
case. That's a problem that will go away much faster than problems in
the XHR interface will.

/ Jonas
Received on Wednesday, 3 November 2010 11:07:51 GMT

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