26988 2014-10-06 17:56:01 +0000 We need a way to parse URLs without decoding the fragment identifier 2014-11-27 10:28:39 +0000 1 1 1 Unclassified WHATWG URL unspecified Other other RESOLVED DUPLICATE 27252 https://html.spec.whatwg.org/#scroll-to-fragid:url-2 P3 normal Unsorted 1 contributor annevk ian mike Ms2ger rubys zcorpan sideshowbarker+urlspec oldest_to_newest 112756 0 contributor 2014-10-06 17:56:01 +0000 Specification: https://html.spec.whatwg.org/ Multipage: https://html.spec.whatwg.org/multipage/#scroll-to-fragid:url-2 Complete: https://html.spec.whatwg.org/#scroll-to-fragid:url-2 Referrer: Comment: We need a way to parse URLs without decoding the fragment identifier (then that should be used in the "indicated part of the document" algorithm) Posted from: 173.8.185.154 User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_9_5) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/39.0.2171.7 Safari/537.36 112759 1 ian 2014-10-06 17:58:22 +0000 Anne, please reassign this to me once you have a way for me to get a non-decoded frag ID. Thanks! 112763 2 ian 2014-10-06 18:12:15 +0000 Actually looks like only Chrome and WebKit do this crazy "scroll to id='te%20st' without decoding the fragid" thing. So maybe this should be WONTFIX, and a new bug should be filed to remove the bad logic in HTML. (IE and Firefox just go to "te st" and ignore id="te%20st" in the tests below.) http://www.hixie.ch/tests/adhoc/html/navigation/fragids/ 112780 3 zcorpan 2014-10-07 08:50:31 +0000 https://code.google.com/p/chromium/issues/detail?id=420981 https://bugs.webkit.org/show_bug.cgi?id=83930 112781 4 annevk 2014-10-07 08:51:36 +0000 What is somewhat weird is that Gecko removes the %20 upon parsing in the fragment component as it does not do that in the path. It's not clear to me Gecko is actually correct here although any kind of change here is probably going to be very painful. 114629 5 rubys 2014-11-07 01:27:43 +0000 Related discussion: http://lists.w3.org/Archives/Public/uri/2014Nov/0000.html 115611 6 annevk 2014-11-27 10:28:39 +0000 *** This bug has been marked as a duplicate of bug 27252 ***