Re: [apps-discuss] Fwd: FW: New Version Notification for draft-kerwin-file-scheme-13.txt

[Matthew Kerwin <[e-mail]>]

On 4 January 2015 at 23:32, Sam Ruby <[e-mail]> wrote:

>
>> For the most part: things that aren't silly (big-endian integer encoding
>> of IPv4 addresses), things that aren't widely touted as obsolete (like
>> backslashes[1]), and as much as possible, things that go against the
>> parent standards (like trying to jimmy "/c|/" into RFC 3986).
>>
>> Importantly, I don't want to include every codepath in every
>> implementation that exists, but I don't want the definition I write to
>> *not* work in any implementations.
>>
>> [1] http://blogs.msdn.com/b/ie/archive/2006/12/06/file-uris-
>> in-windows.aspx
>>
>
> You have a definition for a "windows-path" and a "unc-path".  These are
> unlikely to work on Android or OS/X.
> ​​
>
> ​
> ​


They can (and should) parse them. Then they can (and should) fail to open
them. What's wrong with that?

To get rid of "windows-path", as I said earlier tonight, if someone can
give me better text to deal with roots then by all means please do so.


​
>
> ​​
> Firefox does not appear to support host for file: URIs.
> ​​
>

Firefox does a couple of things in its own way. I've wavered back and forth
about whether it's "file://host/path" or "file:////host/path" (or
"file://///host/path" as Firefox says), and in the end I went with the one
that seems to be fairy widely (if not universally) supported, and in the
spirit of how URIs work in the modern age. There's an open bug somewhere
about how Firefox interprets UNC-type file: URIs. Perhaps if this draft
gets published, in some form or other, that will be the catalyst required
to get said bug fixed/resolved.



-- 
  Matthew Kerwin
  http://matthew.kerwin.net.au/