23550 2013-10-17 16:46:31 +0000 file URL parsing issues 2015-08-14 06:17:23 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED FIXED P2 normal Unsorted 27518 1 annevk annevk d lmm mike rubys travil sideshowbarker+urlspec oldest_to_newest 94906 0 annevk 2013-10-17 16:46:31 +0000 See https://github.com/annevk/url/issues/1 From Domenic: var base = new URL("file:///C:/Users/Domenic/Dropbox/Programming/GitHub/jsdom/test/jsdom/index.js"); var resolved = new URL("/", base); console.log(resolved.href); Gives "file:///", but should give "file:///C:/". 96591 1 annevk 2013-11-20 15:51:24 +0000 http://code.google.com/p/chromium/issues/detail?id=257354 has other cases the specification is not handling. file URLs definitely need more research :/ 115064 2 lmm 2014-11-18 18:14:09 +0000 I wonder if it might be better to treat looking for and resolving "file:" URIs might be best described as a preprocessor, that web applications would use and non-web applications might leave out. 122596 3 annevk 2015-08-13 15:39:28 +0000 It would be interesting to have the results for these: / against file:/// / against file://x/ / against file:///C:/ /C|/ against file:/// /C:/ against file://x/ /C:/ against file:///C:/ 122597 4 annevk 2015-08-13 15:47:25 +0000 And those tests, but then with the input prefixed with "file:", just to make sure. 122605 5 annevk 2015-08-14 06:17:23 +0000 https://github.com/whatwg/url/commit/09cd673a338e7abc552140d950c4f34d7d71362a