Closed Bug 273937 Opened 20 years ago Closed 20 years ago

VxWorks on-line help produces pop-up "c is not a registered protocol"

Categories

(Firefox :: General, defect)

1.0 Branch
x86
Windows 2000
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 219954

People

(Reporter: degood, Assigned: bugzilla)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

The on-line documentation for the Wind-River/vxworks package has an option
to search for a particular entry in their (locally-installed) html-formatted
pages.  This works when IE is the default browser.  Now that I'm using FireFox,
I get an alert pop-up saying "c is not a registered protocol".
The URL shown in IE is something like:
   file:///C:/Tornado/docs/vxworks/ref/ansiString.html#memset
If I enter the URL by hand, it works.
This may be related to bugs: 131143, 131285?

Reproducible: Always
Steps to Reproduce:
1. Bring up Tornado build agent
2. Select help->manuals index.
3. Select any indexed entry in their list

Actual Results:  
Alert! c is not a registered protocol

Expected Results:  
Brought up the browser on a local file.

Since my reproduction needs Tornado installed, it may be hard to reproduce.
Is tnere anything I can do to gather more information?
I've only got the binary Firefox now, but I'm willing to download and build
source if that is needed.
Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.8a6) Gecko/20041209
Firefox/1.0+

See Bug 219954 .

If you have the pages on your local disk, the C: drive, are you able to
run a sed or perl script on them to fix the faulty URIs

href="C:\Tornado/docs ..."  => href="file://C:\Tornado/docs ..." 

?

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