Disabling about:config breaks about:plugins

RESOLVED FIXED

Status

Other Applications
CCK
--
minor
RESOLVED FIXED
12 years ago
12 years ago

People

(Reporter: Robert Parenton, Assigned: mkaply)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

12 years ago
When the CCK is used to disable about:config, about:plugins is disabled as well.

Expected results:
about:plugins functions normally

Actual results:
"about:config has been disabled" is displayed
(Reporter)

Comment 1

12 years ago
This was experienced on Firefox 1.5.0.3 using a .xpi generated by CCK 1.0.1
(Assignee)

Comment 2

12 years ago
that's very strange.

I'm explicitly only overriding about:config

http://lxr.mozilla.org/seamonkey/source/extensions/cck/browser/resources/content/cckwizard/srcfiles/disableAboutConfig.js.in

const ABOUT_CONFIG_CONTRACTID = "@mozilla.org/network/protocol/about;1?what=config";
const NS_ABOUT_REDIRECTOR_MODULE_CID      = Components.ID('{f0acde16-1dd1-11b2-9e35-f5786fff5a66}');

darin, any ideas?
(Assignee)

Comment 3

12 years ago
ok, so basically I was looking for  way to just override one particular contract ID, but I am overriding the entire component because of the CID.

Not sure how to work around this.

Comment 4

12 years ago
You're using the same CID as the default about module? That sounds wrong, you should be making up your own unique CID.
(Assignee)

Comment 5

12 years ago
I tried using my own CID, and I get this:

* Call to xpconnect wrapped JSObject produced this error:  *
[Exception... "'Component does not have requested interface' when calling method
: [nsIModule::getClassObject]"  nsresult: "0x80004002 (NS_NOINTERFACE)"  locatio
n: "JS frame :: chrome://browser/content/browser.js :: loadURI :: line 1569"  da
ta: no]
(Assignee)

Comment 6

12 years ago
Created attachment 223337 [details] [diff] [review]
Fix for problem

I shouldn't have been using the system CID for about:
(Assignee)

Comment 7

12 years ago
fix checked in. 

1.02 will be out soon.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.