[whatwg] handler URI escaping in 4.5.1 appears to be different from encodeURIComponent

[Ian Hickson]

On Wed, 26 Sep 2007, Dan Mosedale wrote:
>
> The escaping specified in 
> <http://www.whatwg.org/specs/web-apps/current-work/#custom-handlers> is 
> slightly different than the escaping done by encodeURIComponent (as 
> described at 
> <http://developer.mozilla.org/en/docs/Core_JavaScript_1.5_Reference:Global_Functions:encodeURIComponent>). 
> Specifically, encodeURIComponent is documented as not escaping:
> 
>    ! * ' ( )
> 
> characters, whereas the spec seems to want these characters to be 
> escaped.  Is this intentional?  If so, what's the motivation?

The spec was changed recently to just require that things that can't be in 
the <query> component of a URI be escaped, instead of saying everything 
must be escaped. Is that ok?

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'