Closed Bug 118139 Opened 24 years ago Closed 24 years ago

nsSample.js doesn't register itself any more

Categories

(Core :: XPCOM, defect)

x86
Windows 95
defect
Not set
normal

Tracking

()

VERIFIED INVALID

People

(Reporter: neil, Assigned: dougt)

Details

Using Build ID: 2002010303 Steps to reproduce problem: 1. delete component.reg 2. mozilla -jsconsole Actual results: Error: compMgr.registerComponentWithType is not a function Source File: file:///C:/MOZILLA/BIN/components/nsSample.js Line: 72
this works for me with a trunk build from this morning. Reporter, please update your tree and verify.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Well it doesn't work in build 2002011003
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
I didn't think that mozilla -jsconsole caused autoregistration.
are you using a Optimized build? Where are you downloading these bits from, if you are not building it yourself?
> I didn't think that mozilla -jsconsole caused autoregistration. The -jsconsole is there to easily display the registration error message. > are you using a Optimized build? > Where are you downloading these bits from, if you are not building it yourself? I'm using http://ftp.mozilla.org/pub/mozilla/nightly/latest/mozilla-win32.zip. The error occurs whenever I unzip and start a new nightly.
Ugh. Do a clean install. nsSample.js IS NOT PART of the build: bash-2.05$ cd components bash-2.05$ ls *.js chatzilla-service.js jsconsole-clhandler.js nsDictionary.js nsHelperAppDlg.js nsLDAPPrefsService.js nsProxyAutoConfig.js nsSidebar.js nsXmlRpcClient.js smime-service.js venkman-service.js If you copy the CURRENT version of nsSample.js into the components directory, it will work fine.
Status: REOPENED → RESOLVED
Closed: 24 years ago24 years ago
Resolution: --- → INVALID
D'oh!
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.