Closed Bug 263506 Opened 20 years ago Closed 20 years ago

In Windows the XUL File association created by firefox is incorrect

Categories

(Firefox :: Shell Integration, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: brianb, Assigned: bugs)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

Windows has "file associations" that map file extensions to a command(s) to
execute to open/view them.  The association created by firefox for XUL files
when executed generates a "c is not a registered protocol" error.  

The problem can be fixed by editing the file association from any explorer
window: hit Tools->Folder Options, then "File Types" and select XUL, hit
"Advanced" and on the Open command hit "Edit" change the command so after the
path to the mozilla executable (firefox.exe perhaps?) it reads: -chrome
"file://%1" (instead of: -chrome "%1")  However, since this does not match the
default setting Mozilla sees that you changed this and asks you "if you want to
make mozilla your default browser" and if you hit yes, it changes it back.

(currently it is setup by the application to read: -chrome "%1"   but since most
paths will begin with "c:/" - you're typical drive letter - it must think c:/ is
 the protocol...)



Reproducible: Always
Steps to Reproduce:
1.Install firefox (or mozilla) or "Set Mozilla to be your default browser"
2.double-click any XUL file

Actual Results:  
receive "c is not a registered protocol" (where "c" may be the drive letter your
xul file was located on)  and no rendering of your pretty form, subsequently
followed by frowning

Expected Results:  
rendered the xul file, subsequently followed by awe
*** Bug 238830 has been marked as a duplicate of this bug. ***
I don't see any way (in testing, or in the code) to have setting Firefox as the
default browser associate it with XUL: starting from scratch, it doesn't. Set
Seamonkey as default, it grabs XUL, then set Firefox as default, Seamonkey still
has XUL. Unless I'm wrong about
http://lxr.mozilla.org/aviarybranch/source/browser/components/shell/src/nsWindowsShellService.cpp#218
being what does the associations, you can only have Firefox handle .xul if you
tell Windows that's what you want yourself.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.