IE6sp1b issues

  • Thread starter Thread starter Gene Black
  • Start date Start date
G

Gene Black

Has anyone gotten the script workaround working correctly for the upcoming
SP1b issues regarding <OBJECT>, <EMBED>, <APPLET> tags?

I have attempted to locate our object reference, applet reference in an
external javascript file and either document.write it to the page or set the
innerHTML of a <DIV> to the string value. Either way it still comes up with
the stupid 'press OK to load page' dialog.

The documents on http://msdn.microsoft.com/ieupdate/activexchanges.asp imply
that would not be the case. Not sure if the test IE6SP1b client is the issue
or the stated workarouond isn't complete. The Object/Applet reference I am
using does need to download the applet from the web server, other than that
there are no other external references (although there are many other PARAM
tags which are passing in values from the page)
 
I am glad that someone else is reporting this.

I even setup some tests where the OBJECT tags were dynamically added to an
existing page using javascript (which the Microsoft page said should not
cause the extra message) but I still get the extra message...

Is anyone able to follow the directions from
http://msdn.microsoft.com/ieupdate/activexchanges.asp and get it to work?

Doug Waddell
CMHC Systems
 
I can get ActiveX controls to work with the NOEXTERNALDATA flag.

For <applets>, if they DO load external data, then the dyanamically-
generate-from-separate-jscript file does not appear to work, either for
my own applet or for an Acrobat plugin.
 
Is there any method for feedback to Microsoft on this?

I ask because I have discovered the following in my testing:
A) If I am imbedding an ActiveX control into a page using an OBJECT tag,
then I do not get the new annoyance prompt.
B) If I use an OBJECT tag to allow for a CAB file to be downloaded via the
Download Component Manager of IE, I get the new annoyance prompt every time
regardless of NOEXTERNALDATA or using javascript to insert the OBJECT tag.

So it would appear that using an OBJECT to execute an existing ActiveX
control is fine, but it could cause a problem if the control is not
currently loaded on that workstation.

Doug Waddell
CMHC Systems
 
It seems the issues that I was experiencing have been resolved as of release
of the new testbed on 10/10/2003 and the addition of known issues including
disabling script debugging in ie.
 
All,

I agree, with the second version of the test bed, the problem that I
reported appears to have been corrected.

Doug Waddell
CMHC Systems
 
Back
Top