D
DianeT
This same problem has cropped up again. Happened the first
time almost a year ago.
I have a website that uses dynamic scripting to load
content into dynamic layers (divs). It seems that anyone
running IE6 with SP1 gets errors citing errors in the
scripting.
The original scripting contained language that called
self.onload events. It seems IE 6 w/SP1 installed does NOT
process these events properly. There is one case that I
know of that has SP1 installed, but also has Q818529 and
Q330994 installed and that person does NOT get script
errors. A person with SP1 and Q822925 installed DOES get
the errors.
Is there a MICROSOFT fix for this obvious bug in the ever-
buggy IE ??
Can anyone venture a guess as to what's in Q818529 and
Q330994 but NOT in Q822925 that would cause the disparity
in IE behavior ??
I REALLY need to find an answer to this. Changing the
self.onload event to window.onload has NOT solved the
problem as we thought it might.
TIA !
time almost a year ago.
I have a website that uses dynamic scripting to load
content into dynamic layers (divs). It seems that anyone
running IE6 with SP1 gets errors citing errors in the
scripting.
The original scripting contained language that called
self.onload events. It seems IE 6 w/SP1 installed does NOT
process these events properly. There is one case that I
know of that has SP1 installed, but also has Q818529 and
Q330994 installed and that person does NOT get script
errors. A person with SP1 and Q822925 installed DOES get
the errors.
Is there a MICROSOFT fix for this obvious bug in the ever-
buggy IE ??
Can anyone venture a guess as to what's in Q818529 and
Q330994 but NOT in Q822925 that would cause the disparity
in IE behavior ??
I REALLY need to find an answer to this. Changing the
self.onload event to window.onload has NOT solved the
problem as we thought it might.
TIA !