W3C home > Mailing lists > Public > whatwg@whatwg.org > October 2012

Re: [whatwg] URL: query encoding

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 30 Oct 2012 17:01:28 +0000 (UTC)
To: Simon Pieters <simonp@opera.com>
Message-ID: <Pine.LNX.4.64.1210301659400.5442@ps20323.dreamhostps.com>
Cc: WHATWG <whatwg@whatwg.org>
On Tue, 30 Oct 2012, Simon Pieters wrote:
> On Fri, 26 Oct 2012 17:23:53 +0300, Anne van Kesteren <annevk@annevk.nl>
> wrote:
> > 
> > Currently encoding the query component of a URL using the document's 
> > encoding affects all URLs with a "relative scheme" (http/ws/file/...). 
> > Should we restrict this to http/https/file so new schemes such as 
> > ws/wss and others will not be affected by this weird legacy quirk?
> 
> So in Opera this quirk does not apply to ws: or wss:.

Even in <a href="ws:"> ? Or just in |new WebSocket()|? (There's no way to 
test non-ws:/wss: in the WebSocket constructor, so asking if it's 
scheme-specific in the constructor can't be answered.)

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 30 October 2012 17:02:03 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:11 GMT