W3C home > Mailing lists > Public > public-webapps@w3.org > April to June 2010

Re: XMLHttpRequest.responseBlob

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 28 Apr 2010 20:27:44 -0700
Message-ID: <w2s63df84f1004282027xf659185aw3483309e9adc4c7e@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Simon Pieters <simonp@opera.com>, Darin Fisher <darin@chromium.org>, Web Applications Working Group WG <public-webapps@w3.org>
On Wed, Apr 28, 2010 at 8:18 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Tue, 27 Apr 2010, Simon Pieters wrote:
>> >
>> > Fine, fine. I've updated HTML5 to rename WebSocket.URL,
>> > EventSource.URL, and Stream.URL to be lowercase.
>>
>> Can you change it back? We've implemented and written tests for
>> WebSocket.URL. WebKit has implemented EventSource.URL and WebSocket.URL.
>
> Do you plan to implement the File API attribute as .URL also?
>
> I really think we should make sure we end up with a consistent naming
> scheme here. If Gecko is the only engine that's going to do .url instead
> of .URL, then I'm happy to change it back (on the assumption that Gecko
> will eventually be forced to change to match). However, it would be a
> pretty mess if we ended up developing APIs in the same year that had
> different cases for the same attributes.

Out of curiosity, why does the year of the API matter?

The way I look at it is: if you tell 100 developers that there is a
property named 'url' on these objects (i.e. tell them, not show them
in writing), how many of them do you think will envision it written in
upper case characters, and how many will envision it in lower case
characters?

/ Jonas
Received on Thursday, 29 April 2010 03:28:40 GMT

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