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

Re: XMLHttpRequest.responseBlob

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 26 Apr 2010 16:05:09 -0700
Message-ID: <v2h63df84f1004261605rbf7f7154v3ddce255f0856448@mail.gmail.com>
To: Ian Hickson <ian@hixie.ch>
Cc: Darin Fisher <darin@chromium.org>, Web Applications Working Group WG <public-webapps@w3.org>
On Mon, Apr 26, 2010 at 3:57 PM, Ian Hickson <ian@hixie.ch> wrote:
> On Mon, 26 Apr 2010, Jonas Sicking wrote:
>> >
>> > Can we please rename .URN to .URL for consistency with the rest of the
>> > platform? It really sticks out like a sore thumb being the only one
>> > that's different... I'm worried people are going to implement it as is
>> > if we don't update the spec soon.
>> For what it's worth, I've implemented it as .url in Firefox.
> Any chance we can get that changed to uppercase for consistency with
> Document.URL? I agree that uppercase is not common in the APIs, but I'd
> rather we keep the platform consistent when it comes to attributes with
> the same name rather than have the APIs depend on the prevailing wisdom at
> the time when they were invented...

We've had this discussion before :)

I initially implemented an uppercased name, but when I was writing
test cases for this property it was incredibly awkward to use the
uppercased version and I kept mistyping it using the lower cased name.

I would rather keep consistency with the hundreds of other properties
that use lower case name, than the single one that use upper case. Add
to that the fact that Document.URL is fairly rarely used.

/ Jonas
Received on Monday, 26 April 2010 23:06:07 UTC

This archive was generated by hypermail 2.3.1 : Friday, 27 October 2017 07:26:24 UTC