That's a pretty bad/quirky example. One problem is that it does no error checking, and it looks to me like the registerChrome() command is going to fail because it never installs the contents.rdf file.
performInstall() does not report an error because it was able to successfully install all the files. Commands that returned an error are skipped -- if the script author does not explicitly call cancelInstall() the engine assumes they weren't important or recoverable. For example, a script could try to install into the global chrome, get "access denied" errors (lack of permissions) and then successfully install into the profile. I believe the language pack install scripts do this. You're much better off examining real scripts used by, say, Mozilla itself, or some of the popular extensions on mozdev.org [EMAIL PROTECTED] wrote: > Hi to everybody who wants to help me! > I have briefly read the article "Creating XPCOM Components" and > downloaded the source code from: http://www.brownhen.com/weblock > Unfortunately I was not able to install the "weblock.xpi" file. Does I > make an obviously mistake? > I installed the xpi file by drag and drop the file to my Mozilla > Browser. The Software Installation Window opened and also the > installation was successful, but when I started the Mozilla Browser > again, the Icon "weblock" in the status line did not occur. How can I > activate the weblock component? > I really appreciate every help!!! _______________________________________________ Mozilla-xpinstall mailing list [EMAIL PROTECTED] http://mail.mozilla.org/listinfo/mozilla-xpinstall
