- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 4 Dec 2009 01:55:50 +0000 (UTC)
On Wed, 2 Dec 2009, Alexey Proskuryakov wrote:
>
> Currently, the Web Sockets API spec says that the WebSocket.URL
> attribute must just return a value that was passed to the WebSocket
> constructor. This doesn't match how many other url accessors work, and
> consequentially, it doesn't match what currently happens in WebKit.
>
> I think it makes more sense to return a resolved URL - e.g. (new
> WebSocket("ws://host/path/../")).URL would return "ws://host/".
I've changed the spec to say that the .URL attribute must return the same
string as is actually used by the protocol spec (i.e. post-resolve).
Whether this does "../" resolution will depend on what the IRI specs end
up saying when we switch to relying on those.
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Thursday, 3 December 2009 17:55:50 UTC