26341 2014-07-15 18:43:32 +0000 file scheme without a base URL 2015-08-14 06:19:48 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED FIXED P2 normal Unsorted 25946 1 simon.sapin annevk mike rubys sideshowbarker+urlspec oldest_to_newest 108963 0 simon.sapin 2014-07-15 18:43:32 +0000 The parser’s scheme state contains: > If url's scheme is "file", set state to relative state. This can happen with a null (not given) base URL, but then the relative state goes on accessing components of the base URL: > "?" > Set url's host to base's host, url's port to base's port, url's path to base's path, url's query to the empty string, and state to query state. Test cases: new URL("file:") new URL("file:?foo") new URL("file:#foo") The parsing algorithm could be clearer with a separate handling of file: URLs between the scheme state and the path/query/fragment states. 114569 1 rubys 2014-11-05 21:34:48 +0000 http://intertwingly.net/projects/pegurl/url.html separates out file: URLs. Should this approach be adopted, what more needs to be done here? 122606 2 annevk 2015-08-14 06:19:48 +0000 Thank you Simon. I fixed this with this commit, which introduces several new file-specific states: https://github.com/whatwg/url/commit/09cd673a338e7abc552140d950c4f34d7d71362a It also resolves a number of other issues around file URLs, though it'll still need more verification and tests.