Existant versions of the Netscape 6.X browser installers make assumption about how the plugin is to be installed. These assumption are based on one method of plugin to browser connection (NSGetFactory). This method of connection is slated to go away at some future date, (replaced by NSGetModule, for now).

The beta-3 release of merlin has been updated to use the NSGetModule method (which is supported in all current browsers, but broken Netscape 6.2), and removed NSGetFactory. Unfortunatly, Netscape's installers for these browsers were not updated, so that when Netscape is installed after Java the Netscape installers try to connect the two using NSGetFactory.

Given this, the Merlin version of the plugin needs to support both methods of browser to plugin connection so NSGetFactory method should be put back in and NSGetModule should be left in as well for future release (such as the Mozilla trunk). A bug has been filed against Netscape for them to update their installers in future version.

What our installers should do is still up for consideration. Idealy, we should just support the NSGetModule method, but it might be nice if we could make a special case exception for Netscape 6.2 versions of the browser. They will also need to be able to remove an existing NSGetFactory installation and replace it with a NSGetModule installation, when appropriate (ie anytime Java is installed after the browser for all Netscapes/Mozillas other then 6.2)