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

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

From: (unknown charset) Ian Hickson <ian@hixie.ch>
Date: Tue, 4 Apr 2006 23:11:26 +0000 (UTC)
To: (unknown charset) Web APIs WG <public-webapi@w3.org>
Message-ID: <Pine.LNX.4.62.0604042306340.21459@dhalsim.dreamhost.com>

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).

Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 4 April 2006 23:11:35 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:20 UTC