On 16 Oct 2006 at 15:42, Max Carlson wrote:
> This is a long standing bug - after several conversations with d~1 I was
> never able to reproduce. I tried many different versions of IE. It
> sounds like it comes down to localization or something else that makes
> his version of IE different from ours - QA hasn't been able to reproduce
> this issue either
Max
That thread was started by another user with similar (albeit rare) symptoms of lzx.swf
rendering blank in IE (some versions). Encouraging that I am no more in a minority of one.
Although in the minority, a few other users of IE have since reported similar problems in
laszlosystems forum. EOLAS was another issue.
LaszloSystems QA may not have reproduced the same symptoms in IE .. but that does not
mean they are not still there (for some IE users)!
..
Problem (in my IE browser) first arose post lps-3.1 .. when you dropped using nested
<object><embed> (Satay method) in embed.js.
See line 158/159 in embed.js ..
"// write out a hidden div with an object tag to force an upgrade in IE only"
To test this theory I tried using an earlier version (3.0.2) of embed.js and this cured my IE
rendering problem.
But I decided to switch permanently to SWFObject.js.
The symptoms were reported here ..
..
Also the question was raised in initial thread .. is there a case for dropping embed.js and
relacing with SWFObject.js?
Adobe.com has endorsed the SWFObject code .. see reference to 3rd party software at
Adobe site.
Added SWFObject features include ExternalInterface (Flash 8) and Java Integration Kit (pre
Flash 8).
..
In this thread ..
for backwards compatibility I considered using a "hybrid" solution - i.e. cutting out the
<object></object> block of code in embed.js and replacing with a call to SWFObject.js.
But this seems to be a retrograde step and duplication of code. So abandoned.
Better in my view to switch to using SWFObject.js entirely, and add any additional
backwards compable functions like _lzSetCanvasAttribute (but using SWFObject API to
implement set canvas attribute ). It is easy to pass vars via SWFObject.
d~l
