Open Bug 640495 Opened 13 years ago Updated 1 year ago

Win32 only: forward slashes are not supported in command line integration


(Firefox :: File Handling, defect)

Windows Server 2003





(Reporter: designfu, Unassigned)


(Keywords: reproducible)

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv: Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv: Gecko/20101203 Firefox/3.6.13 ( .NET CLR 3.5.30729)

Command lines like

firefox c:/temp/test.html
firefox c:\temp/test.html

fail to open properly, but are supported on all (?) standard Win32 apps. Firefox currently requires backslash.

Reproducible: Always

Steps to Reproduce:
1. notepad c:\temp/test.html
2. firefox c:\temp/test.html
2. firefox c:/temp/test.html
Actual Results:  
"Firefox doesn't know how to open this address, because the protocol (c) isn't associated with any program."

Expected Results:  
Open as does notepad, IE, ...
Keywords: reproducible
Component: Shell Integration → File Handling
Product: Firefox → Core
This is incorrect syntax. By default, Firefox interprets command line parameters as a URL. If you want to pass a local file, you need to use firefox -file c:/temp/test.html in which case I'm pretty sure that forward slashes will work.
Closed: 13 years ago
Resolution: --- → INVALID
firefox.exe -file c:/temp/test.html does not work, sorry.

The result is an attempt to access file:///C:/PROGRA~2/Mozilla%20Firefox/c:/temp/test.txt or the like.
Resolution: INVALID → ---
QA Contact: shell.integration → file-handling
Just before Firefox 3.0, some irresponsible person made a half-baked change to command-line processing that resulted in all command line arguments being disabled when running on Windows.  I complained about it at the time in bug 355889 comment 12, and was told to shut up or else (see later comments in that bug).

It may be time to abandon Mozilla if the project is owned by that kind of bullies.
Product: Core → Firefox
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.