That's easy to answer:
Copy the code from Firefox that allows it to handle both local paths
and URLs correctly and incorporate that into Chrome.
On Jan 8, 5:15 am, Paweł Hajdan, Jr. <phajdan...@chromium.org> wrote:
> We havehttp://crbug.com/4436, and the problem is that if you launch
> chrome index.html (with index.html in the current directory) it will
> try to navigate tohttp://index.html/instead. This behavior is useful
> for cases like chromewww.google.com, and generally I don't see a good
> solution to this issue other than WontFix. Other shell launchers are
> expected to pass a full path I think.
>
> explorer.exe behaves in a reverse way (www.google.comfails,
> index.html succeeds).
>
> In firefox both local relative paths and urls without http work.
>
> What should we do for Chrome?
--
Chromium Developers mailing list: chromium-dev@googlegroups.com
View archives, change email options, or unsubscribe:
http://groups.google.com/group/chromium-dev
