W3C home > Mailing lists > Public > whatwg@whatwg.org > December 2008

[whatwg] Resolving URLs

From: Ian Hickson <ian@hixie.ch>
Date: Mon, 29 Dec 2008 10:23:57 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0812291023240.24109@hixie.dreamhostps.com>
On Fri, 27 Jun 2008, Adam Barth wrote:
>
> In <http://www.whatwg.org/specs/web-apps/current-work/#resolving>, the 
> spec says:
> 
> "If the URL to be resolved was passed to an API
>     The base URL is the document base URL of the script's script 
> document context."
> 
> I believe browsers differ on this point.  When resolving a URL received 
> from a script, there are three likely sources of a base URL:
> 
> 1) The script's script document context (i.e., the document of the
> window object lexically in scope).
> 2) The document of the window object dynamically in scope.
> 3) The document to which the API belongs.
> 
> I'm working on a test suite to reverse engineer the behavior of current 
> browsers and will report my findings.

The spec has changed now, but it is still based on a feature of the script 
right now. I would be interested in hearing the results of your research.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Monday, 29 December 2008 02:23:57 UTC

This archive was generated by hypermail 2.3.1 : Monday, 13 April 2015 23:08:46 UTC