This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 27518 - remove any and all normative definition of file:// handling
Summary: remove any and all normative definition of file:// handling
Status: RESOLVED INVALID
Alias: None
Product: WHATWG
Classification: Unclassified
Component: URL (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: Unsorted
Assignee: Sam Ruby
QA Contact: sideshowbarker+urlspec
URL:
Whiteboard:
Keywords:
Depends on: 25946
Blocks: 23550 27517
  Show dependency tree / graph
 
Reported: 2014-12-04 15:34 UTC by Sam Ruby
Modified: 2015-08-13 08:18 UTC (History)
5 users (show)

See Also:

Attachments

Description Sam Ruby 2014-12-04 15:34:12 UTC 
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.
Comment 1 Sam Ruby 2014-12-04 15:38:36 UTC 
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.
Comment 2 Jonas Sicking (Not reading bugmail) 2014-12-04 21:16:49 UTC 
That seems fine with me.
Comment 3 Edward O'Connor 2014-12-09 23:36:07 UTC 
Just noticed someone's working on defining file: over at the IETF: http://www.ietf.org/id/draft-kerwin-file-scheme-13.txt
Comment 4 Sam Ruby 2014-12-10 01:25:11 UTC 
Thanks, Ted!

Following up: http://www.ietf.org/mail-archive/web/apps-discuss/current/msg13473.html
Comment 6 Anne 2015-08-13 08:18:12 UTC 
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.