If you would like to use this plugin it is strongly recommended that you fill in these lists (trusted domains, controls), choose a unique MIME Type for your purposes, and sign the XPI. It is provided for the mere purpose of testing and performing simple POCs. It has no predefined lists of trusted sites/controls. The source stored in the SVN repository here can be considered 'vanilla' code. The URL must match the list of trusted domain if one exists.CAB Download - You can specify a URL for downloading a CAB with the control if it does not exist.Events - You can bind Javascript function to events.Parameters - You can pass parameters to the embedded control.Scriptable - Fully scriptable from Javascript, calling methods, retrieving/setting property values, etc.

The plugin aims to provide full support for embedding ActiveX controls. Again, trying to use any other control will fail. The plugin can be compiled with a list of trusted control CLSIDs/PROGIDs.It will refuse to load ActiveX objects for any other domain. The plugin can be compiled with a list of trusted domains that will be allowed to use it.The plugin will not work on regular object tags that are used to embed ActiveX controls in IE.

To that end several measures have been taken: This plugin does not aim to reduce the security of FF. The lack of support for ActiveX controls in FF is definitely one of its strong points where security is concerned. It does not work transparently in sites that use ActiveX objects. The plugin registers its own MIME Type - meaning that currently web pages need to be written with this plugin in mind. Many times that native code already exists in the form of an ActiveX control. Sometimes, to create an ideal user experience you have to be able to use some native code. This plugin was written to try and reduce the gap between IE and FF when it comes to content that can be used in web applications. References to Firefox hold true for Chrome as well. The contents of this file were written long ago.

Activex on firefox