W3C home > Mailing lists > Public > public-webapps@w3.org > July to September 2011

Re: [XHR2] responseType and response properties

From: Jonas Sicking <jonas@sicking.cc>
Date: Fri, 12 Aug 2011 18:14:05 -0700
Message-ID: <CA+c2ei_j5poO0JFF5R5SiOm1d9PYu8VyZqukBtiM7BgPR-SFew@mail.gmail.com>
To: Chris Rogers <crogers@google.com>
Cc: Webapps WG <public-webapps@w3.org>
On Fri, Aug 12, 2011 at 5:43 PM, Chris Rogers <crogers@google.com> wrote:

> Hi Jonas, sorry about the late reply - comments inline:
>
> On Sat, May 21, 2011 at 12:36 AM, Jonas Sicking <jonas@sicking.cc> wrote:
>
>> Hi All,
>>
>> Firefox 6 is going to add support for the the new responseType and
>> response properties. We would have liked to release these as
>> moz-prefixed properties, but it appears that webkit has already
>> shipped them unprefixed, thus there's not much point in prefixing.
>> Both because we likely can't fix bugs in them anyway, and because
>> sites have already started depending on them.
>>
>
>
>
>>
>> I'd really like to reiterate that we need to be careful about
>> releasing newly minted APIs unprefixed. Even in the case where we here
>> on the list agree on the desired behavior. The Blob.slice mess (which
>> we fortunately managed to save last minute) is a good example of why
>> we should give API time to mature before unprefixing.
>>
>
> Sorry, about that.  I thought we had good agreement about the API.
>

Even on things where there's agreement here it's a good idea to prefix since
once we reach a wider audience (non W3C people as well as developers)
there's a good change that problems will be found.

/ Jonas
Received on Saturday, 13 August 2011 01:15:12 GMT

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