- From: Jerry Mead <jerrym@meadroid.com>
- Date: Mon, 13 Oct 2003 19:18:36 +0100
- To: <public-web-plugins@w3.org>
V .02 of the IE6SP1b test builds was released on 10th October here: http://msdn.microsoft.com/ieupdate/ It fixes the 'first time install' behavior I described earlier (below). Those who are still seeing prompts when using .js writeIn might need to check this, from 'Known Issues': " If you have the Microsoft Script Debugger enabled, Web pages using the external .JS file mechanism may continue to prompt. This can be eliminated by running without the Script Debugger enabled. " That has been confirmed, here at least. Jerry Mead http://www.meadroid.com/ ----- Original Message ----- From: "Jerry Mead" <jerrym@meadroid.com> To: <public-web-plugins@w3.org> Sent: Thursday, October 09, 2003 1:41 AM Subject: Undocumented functionality in v.01 test build of IE6sp1b > > If you dynamically write in (via the 'Microsoft-recommended' method) an > ActiveX object for a control *that is not already installed on a client > machine* and then access that document from a web server, you will see the > usual security prompt followed by a dialog entitled "ActiveX installation" : > "Press OK to continue installing". > > This dialog is not documented on the docs for the IE6sp1b test build, and if > we follow through the logic that dynamically written-in content does not > infringe the Eolas patent then it should not be appearing anyway. > > I'm assuming that this is a bug in IE6sp1b v.01 that was missed in test. > > I sincerely hope so, otherwise it rather defeats the object of asking our > corporate customers to re-script vast numbers of documents (none of which, > Michael Wallent may be surprised to learn, leverage our controls to 'deliver > advertising'). > > Jerry Mead > http://www.meadroid.com/ > >
Received on Monday, 13 October 2003 14:19:00 UTC