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

Re: [whatwg] URL: query encoding

From: Simon Pieters <simonp@opera.com>
Date: Tue, 30 Oct 2012 17:43:42 +0200
To: WHATWG <whatwg@whatwg.org>, "Anne van Kesteren" <annevk@annevk.nl>
Message-ID: <op.wmz3e4b6idj3kv@dhcp26-236.enst.fr>
On Tue, 30 Oct 2012 17:20:33 +0200, Simon Pieters <simonp@opera.com> 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:. We have a test  
> case for this. I believe the spec required this at the time we  
> implemented it. Firefox passes the test as well, but Chrome fails it  
> (Chrome has the quirk). I don't know what IE does. I tentatively suggest  
> we go with Opera/Firefox here and limit this quirk so it does not apply  
> to ws: or wss:.

The above applies to what gets sent over the wire when using the  
WebSocket(...) constructor. For <a href>, the results are different:

http://simon.html5.org/test/url/url-encoding.html

I don't have an opinion at this point about what to do here.

>> Is
>> that something implementors would consider following?
>>
>> The parsing section of http://url.spec.whatwg.org/ has this as an open
>> issue for now.
>>
>>
>
> cheers


-- 
Simon Pieters
Opera Software
Received on Tuesday, 30 October 2012 16:44:24 GMT

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