[Bug 10410] On getting, should the UA percent-decode document.location.hash? It's not clear.

http://www.w3.org/Bugs/Public/show_bug.cgi?id=10410

--- Comment #5 from Adam Barth <w3c@adambarth.com> 2010-09-30 06:54:27 UTC ---
> "#%3F" seems to be the answer per spec now, but I'll defer to Adam.

I have data on all this stuff, but I haven't paged it into memory recently. 
Here's a test that covers this case:

http://trac.webkit.org/export/LATEST/trunk/LayoutTests/fast/url/segments.html

Chrome:
PASS segments('http://foo/path;a??e#f#g') is
'["http:","foo","0","/path;a","??e","#f#g"]'

Safari:
FAIL segments('http://foo/path;a??e#f#g') should be
["http:","foo","0","/path;a","??e","#f#g"]. Was
["http:","foo","0","/path;a","??e","#f%23g"].

Firefox:
FAIL segments('http://foo/path;a??e#f#g') should be
["http:","foo","0","/path;a","??e","#f#g"]. Was
["http:","foo","","/path","??e","#f#g"].

Opera:
FAIL segments('http://foo/path;a??e#f#g') should be
["http:","foo","0","/path;a","??e","#f#g"]. Was
["http:","foo","80","/path;a","??e","#f#g"].

IE: (untested)

(Note that "PASS" is arbitrarily set to whatever Chrome does because Brett
picked these test cases.)

Generally, this stuff is a mess.  We'd want to test IE to be sure, but it looks
like the "right" answer here is "#f#g".

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Thursday, 30 September 2010 06:54:29 UTC