I'm fine with the Firefox way. It seems OK for command line inputs to
require more strictly validated inputs for URLs, and to follow shell
semantics for handling files.
-Ben
On Wed, Jan 13, 2010 at 7:42 AM, Paweł Hajdan jr <phajdan...@gmail.com> wrote:
> Michał, Chris: could you comment on security aspects and give some
> recommendations?
>
> Ben, could you comment on the "user interaction / usability" aspect?
> We have few choices here, I'm not sure which one is preferred.
>
> On Mon, Jan 11, 2010 at 23:23, Benjamin Smedberg <bsmedb...@gmail.com> wrote:
>> For what it's worth, the way Firefox solves this is:
>>
>> * Check if the file is an absolute file path
>> ** on Windows, X:\... or \\...
>> ** on Posix, /...
>> * Otherwise, it's a URL relative to the current working directory
>> ** So index.html resolves using the URL machinery to
>> file:///c:/cwd/index.html
>> ** while http://www.google.com resolves to itself
>>
>> This doesn't deal with the case firefox.exe www.google.com (which would try
>> to resolve as a file), but we decided not to care about this case. We do
>> have the explicit firefox.exe -url www.google.com which will perform URI
>> fixup to guess the correct URL.
>>
>> --BDS
>>
>>
>> --
>> Chromium Developers mailing list: chromium-dev@googlegroups.com
>> View archives, change email options, or unsubscribe:
>> http://groups.google.com/group/chromium-dev
>>
>
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
