21175 2013-03-03 00:59:32 +0000 "Last string" of path is undefined if path has no strings while a URL is parsed 2013-03-04 09:45:38 +0000 1 1 1 Unclassified WHATWG URL unspecified PC Windows NT RESOLVED FIXED P2 normal Unsorted 1 poccil annevk mike sideshowbarker+urlspec oldest_to_newest 83905 0 poccil 2013-03-03 00:59:32 +0000 From the parsing algorithm: ---- If buffer is ".." and c is one of EOF code point, "/", and "\", set the last string in url's path to the empty string. Otherwise, if buffer is "..", remove the last string from url's path. ---- For URLs like: http://example.com/../../filename , when there are no strings in the path yet, after the first "../" is read, it's undefined what happens. Does it trigger an error? Does the parser return failure? Or is that step just simply ignored? This may also affect this rule, found elsewhere in the algorithm: ----- Set url's host to base's host, url's port to base's port, url's path to base's path, then remove url's path's last string, set state to relative path state, and decrease pointer by one. ----- 83910 1 annevk 2013-03-03 13:17:37 +0000 Yeah, I suppose this should all just become pop url's path and append to url's path, with replace being that combination. 83911 2 annevk 2013-03-03 13:26:40 +0000 https://github.com/whatwg/url/commit/33b15c97d762e9f100126f66e2bec4234a3779df 83913 3 poccil 2013-03-03 15:05:07 +0000 Thanks for your change. I think having it say "pop url's path if possible" would make it better, to further make it clear. 83925 4 annevk 2013-03-04 09:45:38 +0000 Fair enough: https://github.com/whatwg/url/commit/a421bbc781d923e6cfb84f10bc5c21cd4a164882