Closed Bug 303878 Opened 19 years ago Closed 19 years ago

Launching Firefox 1.0.6 on chrome URL fails.

Categories

(Firefox :: General, defect)

x86
Windows 2000
defect
Not set
major

Tracking

()

VERIFIED DUPLICATE of bug 301073

People

(Reporter: mozilla, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-GB; rv:1.7.10) Gecko/20050717 Firefox/1.0.6

When launching Firefox on the command line, one can specify the start page.  The
following work fine:
  firefox.exe http://google.com
  firefox.exe about:config
But opening an chrome URL fails:
  firefox.exe chrome://jslib/content/icons/jslib-icon.png
  (this assumes that one has jslib installed)
No error message is printed, no browser window opens.  The computer churns for a
few seconds but nothing appears.

This is new.  Firefox 1.0.4 would open a chrome URL without problems.  Firefox
1.0.6 does not.  This completely smashes the application we've developed, in
that our clients can no longer launch it.

Reproducible: Always

Steps to Reproduce:
1. Verify that chrome://jslib/content/icons/jslib-icon.png can be loaded.
2. Close Firefox.
3. On the command line type:
  firefox.exe chrome://jslib/content/icons/jslib-icon.png

Actual Results:  
Nothing happens.

Expected Results:  
Firefox should open and display the PNG.

We've seen this in Windows 2000, and our clients are reporting the same in XP.
I believe this was done deliberatly to bypass a possible security bug, it's
still locked at the moment but Bug 298255 will have more details when it's
unlocked. See http://www.mozilla.org/security/announce/mfsa2005-53.html for now.

You can bypass this by explicitly specifying the -chrome switch, e.g.:

firefox.exe -chrome chrome://jslib/content/icons/jslib-icon.png

*** This bug has been marked as a duplicate of 301073 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.