VK said:
As the last ressort before to give up: many browsers (including Firefox
and "possibly" Opera) are acting funny on <object> elements.
Get rid of <object> section and try your flash on pure <embed>. Please
let know if it helps.
My impression was that, at this point, the concern was with the alert
that failed to appear on some browsers at this point, but, yes, the
code to embed flash can be tricky and is a likely location for
problems. Here is the object the poster used:
OBJECT
CLASSID="clsid
27CDB6E-AE6D-11cf-96B8-444553540000"
WIDTH="100%"
HEIGHT="100%"
CODEBASE="
http://download.macromedia.com/pub/shockwave/cabs/flash/swflash.cab"
ID=testmovie>
<PARAM NAME="MOVIE" VALUE="flash-to-javascript.swf">
<PARAM NAME="PLAY" VALUE="false">
<PARAM NAME="LOOP" VALUE="false">
<PARAM NAME="QUALITY" VALUE="high">
<PARAM NAME="SCALE" VALUE="SHOWALL">
<EMBED
NAME="testmovie"
SRC="flash-to-javascript.swf"
WIDTH="100%"
HEIGHT="100%"
PLAY="false"
LOOP="false"
QUALITY="high"
SCALE="SHOWALL"
swLiveConnect="true"
PLUGINSPAGE="
http://www.macromedia.com/go/flashplayer/">
</EMBED>
</OBJECT>
The object is an ActiveX object as indicated by the 32 digit ActiveX
id, in this case unique for flash. For flash,the ActiveX object will
work only on IE and close relatives. If the ActiveX object is fouled or
ActiveX is turned off, the flash movie will not show up on IE if the
code is written only for ActiveX. If the ActiveX path is taken, the
embed contained within the AX object is ignored as if it were not
there. However, if ActiveX is not supported, the embed path is taken.
This type of code gives the W3C validator fits, but it is widely used
by huge media sites and usually seems to work. There are ways to avoid
using both embed and ActiveX that will validate and that will work on
most recent browsers.