Closed
Bug 294347
Opened 20 years ago
Closed 19 years ago
FF disregards network.protocol-handler.app.<protocol> in Windows version
Categories
(Firefox :: Shell Integration, defect)
Tracking
()
RESOLVED
EXPIRED
People
(Reporter: qwer1304, Unassigned)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 (ax) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4 (ax) FF v1.0.4 (and earlier) disregards network.protocol-handler.app.<protocol> in Windows version. Instead, it fetches the application to run from the registry (HKEY_CLASSES_ROOT\<protocol>) network.protocol-handler.external.<protocol> has the following effect: 1.When true, the application from the registry is invoked 2.When false, nothing happens network.protocol-handler.warn-external.<protocol> works as expected Reproducible: Always Steps to Reproduce: 1.set network.protocol-handler.external.<protocol> to true 2.set network.protocol-handler.app.<protocol> to an application of your choice 3.try to access <protocol>://xxx.yyy 4.observe that your application is not invoked Actual Results: the application registered in HKEY_CLASSES_ROOT\<protocol> is invoked Expected Results: the application in network.protocol-handler.app.<protocol> should have been invoked
Updated•20 years ago
|
Component: Preferences → Build Config
Product: Firefox → Core
Version: unspecified → 1.7 Branch
Updated•20 years ago
|
Component: Build Config → OS Integration
Product: Core → Firefox
Version: 1.7 Branch → unspecified
Comment 1•19 years ago
|
||
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
Comment 2•19 years ago
|
||
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•