27518 2014-12-04 15:34:12 +0000 remove any and all normative definition of file:// handling 2015-08-13 08:18:12 +0000 1 1 1 Unclassified WHATWG URL unspecified All All RESOLVED INVALID P2 normal Unsorted 25946 23550 27517 1 rubys rubys annevk eoconnor jonas mike rubys sideshowbarker+urlspec oldest_to_newest 115930 0 rubys 2014-12-04 15:34:12 +0000 This bug is opened on behalf of Jonas Sicking, based on http://lists.w3.org/Archives/Public/public-webapps/2014OctDec/0526.html Original comment: To be clear, I'm proposing to remove any and all normative definition of file:// handling from the spec. Because I don't think there is interoperability, nor do I think that it's particularly high priority to archive it. 115931 1 rubys 2014-12-04 15:38:36 +0000 I think that this proposal is a bit too extreme. An example of interoperable behavior: https://url.spec.whatwg.org/interop/urltest-results/a4633c6047 I'd propose only dropping things known not to be interoperable. 115954 2 jonas 2014-12-04 21:16:49 +0000 That seems fine with me. 116080 3 eoconnor 2014-12-09 23:36:07 +0000 Just noticed someone's working on defining file: over at the IETF: http://www.ietf.org/id/draft-kerwin-file-scheme-13.txt 116083 4 rubys 2014-12-10 01:25:11 +0000 Thanks, Ted! Following up: http://www.ietf.org/mail-archive/web/apps-discuss/current/msg13473.html 116615 5 rubys 2014-12-20 22:22:40 +0000 Related: https://mailarchive.ietf.org/arch/msg/apps-discuss/KyxFLw2FCwv7CSpiWAmLr8Ha7vc 122581 6 annevk 2015-08-13 08:18:12 +0000 Thank you for this report, but I do not think that leaving file URL parsing undefined is helping anyone. E.g., libraries outside browsers use this parsing algorithm to support file URLs on their systems. We will need to fix bugs where things are not interoperable (fixes welcome), or even allow different codepaths depending on the OS (though I hope not), but as filed I do not think this is helpful.