W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

Re: ISSUE-67: Should resolution of relative URI references sent to location be defined in JS bindings or generally?

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 05 Apr 2006 02:43:41 -0700
Message-ID: <4433914D.4030406@sicking.cc>
To: Ian Hickson <ian@hixie.ch>
Cc: Web APIs WG <public-webapi@w3.org>

Ian Hickson wrote:
> On Tue, 4 Apr 2006, Web APIs Issue Tracker wrote:
>> Assigning a relative URI reference to window.location (or using 
>> location.assing() or location.replace()) from JS has an odd quirk: the 
>> URI is resolved relative to the location of the window currently 
>> executing code, rather than the location it is actually being assigned 
>> to. This is kind of weird, and also doesn't make sense for languages 
>> other than ECMAScript. I can imagine the following possibilities:
> 
> We have to keep this behaviour in JS.
> 
> I don't care how it works in other languages, but I would encourage using 
> a solution that makes the JS behaviour prominent in the spec (i.e. mention 
> this in the part of the spec that defines things like location.replace() 
> and the magic location setter).

Yeah, I agree with Ian. I think 4 sounds like the best option. If we 
define this in the bindings section or in the main spec I don't have a 
strong oppinion on.

/ Jonas
Received on Wednesday, 5 April 2006 09:43:44 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT