This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
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.
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.
That seems fine with me.
Just noticed someone's working on defining file: over at the IETF: http://www.ietf.org/id/draft-kerwin-file-scheme-13.txt
Thanks, Ted! Following up: http://www.ietf.org/mail-archive/web/apps-discuss/current/msg13473.html
Related: https://mailarchive.ietf.org/arch/msg/apps-discuss/KyxFLw2FCwv7CSpiWAmLr8Ha7vc
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.