On 10/29/12 5:00 AM, Anne van Kesteren wrote:
But note that it would be a bit odd of file://c:/ claimed to have a host of
"c" with a default port or some such...
Maybe I should introduce a "file host state" that supports colons in
the host name (or special case the "host state" further, but the
former seems cleaner).
I don't think that's particularly desirable. The "c:" is totally part
of the path; treating it otherwise would just be confusing. Imo.
Most browsers seem to fail currently on input
such as "file://c:/" but this is on a Mac
Yes, doing that on a Mac would just be wrong....
I would prefer having the parsing be consistent though.
You mean across Windows and non-Windows? I'm not sure that's viable.
-Boris
