User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5) Gecko/20031007 Is there any plans to support the "Microsoft License Manager Component"? Currently Netscape, Mozilla, and Firebird either natively support hosting ActiveX controls or through the Mozilla Active Hosting Plugin, and do a pretty good job of it in the latest releases! However, Netscape/Mozilla/Firebird crash when instantiating the Microsoft License Manager Component, which is required when hosting Licensed ActiveX Controls through LPK files. e.g. of the object tag for the Microsoft License Manager Component... <object CLASSID="clsid:5220cb21-c88d-11cf-b347-00aa00a28331" VIEWASTEXT> <param name="LPKPath" value="/download/MyLPKfile.lpk"> </object> ...results in "Mozilla ActiveX control and plugin support. The plugin performed an illegal operation. You are strongly advised to restart Navigator." when attempting to create the object above. Any hopes on supporting the "Microsoft Licese Manager Component?" Reproducible: Always Steps to Reproduce: 1. Place Microsoft License Manager Component object before other License ActiveX Objects. 2. To truly fix problem, I can send you a CAB file that contains the "licensed- version" of our ActiveX components so that you can test with an ActiveX component that requires a license or modify the webpage to use an ActiveX component that requires a license to run. This is not a problem with our component, only with the Microsoft License Manager Component. 3. Open Web Page. Actual Results: Error Message Pops-up... "Mozilla ActiveX control and plugin support. The plugin performed an illegal operation. You are strongly advised to restart Navigator." Expected Results: Not shown error, and the "Microsoft License Manager Component" should be able to pass license information using the specified LPK file to any ActiveX control on the page that requires it.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.