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 19687 - It's not entirely clear to me how this algorithm can be correct as Gecko/Opera appear to decode %-sequences when parsing the URL so you cannot have fragid and decoded fragid.
Summary: It's not entirely clear to me how this algorithm can be correct as Gecko/Oper...
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: HTML (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: Unsorted
Assignee: Ian 'Hixie' Hickson
QA Contact: contributor
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-10-24 12:24 UTC by contributor
Modified: 2012-10-29 22:00 UTC (History)
3 users (show)

See Also:

Attachments

Description contributor 2012-10-24 12:24:29 UTC 
Specification: http://www.whatwg.org/specs/web-apps/current-work/
Multipage: http://www.whatwg.org/C#the-indicated-part-of-the-document
Complete: http://www.whatwg.org/c#the-indicated-part-of-the-document

Comment:
It's not entirely clear to me how this algorithm can be correct as Gecko/Opera
appear to decode %-sequences when parsing the URL so you cannot have fragid
and decoded fragid.

Posted from: 212.238.236.229 by annevk@annevk.nl
User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_8_2) AppleWebKit/537.16 (KHTML, like Gecko) Chrome/24.0.1297.0 Safari/537.16
Comment 1 Anne 2012-10-24 12:39:12 UTC 
Actually, it seems only Gecko does this. Opera only does it in the address bar. Lets not do this then.
Comment 2 Ian 'Hixie' Hickson 2012-10-29 22:00:51 UTC 
Yeah, this was an area with dubious interop, but I went with what seemed to match the most browsers. Let me know if the URL spec ends up making it not work after all, but I think, as you say, that it is still ok.