This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 24164 - Percent-decode characters that do not require percent-encoding?
Summary: Percent-decode characters that do not require percent-encoding?
Status: RESOLVED WONTFIX
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: PC Linux
: P2 normal
Target Milestone: Unsorted
Assignee: Anne
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-12-23 18:56 UTC by Santiago M. Mola
Modified: 2014-01-15 11:09 UTC (History)
1 user (show)

See Also:

Attachments

Description Santiago M. Mola 2013-12-23 18:56:06 UTC 
http://example.com/%61 is parsed as http://example.com/a by IE 10 and Chrome 31, while it is preserved as is by Safari 5 and Firefox 25.

Being the behaviour of both IE and Chrome it seems a good idea to set it as the standard practice?
Comment 1 Anne 2014-01-11 16:04:55 UTC 
Note that they only do this for URLs with relative schemes and only in the path component. It's a rather special case which is why I decided against it.
Comment 2 Anne 2014-01-15 11:09:10 UTC 
WONTFIX for now. I decided against this. We'll see what browser vendors say when they start implementing this.