Sooooo it looks like IE7 has started to hate SWFObject...
Have any of you guys actually gotten AC_RunActiveContent to ever fucking WORK? It seems to be an utter POS.
I want my movie to display "fullscreen" within the browser, vertically and horizontally centered, without scaling when the browser is resized.
What's the NEW NEW SUPERDUPEREST way to do this in 2009?
Fanku!
How does IE7 hate SWFObject?
I'm not having any IE7/swfobject problems.
swfobject and/or swffit
IE6/7 is very slow even on fast machines to resolve flashvars including (stage), it makes a difference how you embed flash even down to how you use swfobject ( head or body and the way you set parameters etc...) and obviously the speed and loading of the computer.
IE seems to be particularly useless so it tends to be more a PC issue something you can miss if developing on a mac, but given enough flashvars other browsers will also fail in differing amounts.
The problem mostly effects interactive banners since larger movies usually parsing XML before really making much use of stage or any flashvars.
Anyway a solution that seems to be effective is to wait for the flashvars object to populate.
// I use similar in a class but something like this timeline code should work stop(); var here: Sprite = this; var _timer:Timer = new Timer( 40, 0 ); _timer.addEventListener( TimerEvent.TIMER, isReady ); _timer.start();
function isReady( e: TimerEvent ) { var notEmpty: Boolean = false; for( var all: String in LoaderInfo( _level0.loaderInfo ).parameters ) { notEmpty = true; break; } if( notEmpty ) { _timer.stop(); here.gotoAndStop(2); } }
Also for IE6/7 use actual pixel size not percent in the swfobject declaration.
Good to know JLM.
Whenever I'm dealing with code in Flash that works with the Stage size, I always set an initial delay of like 200 milliseconds or so before I try and do anything, since I've run into Stage issues in the past, but didn't really know what the cause was.
But that's very interesting to know that the placement of the JS (head versus body) can affect IE's performance, and also interesting to know about using actual pixel values rather then percentages in the swfobject declaration.
I've never run into a problem of Flash not responding to flashvars passed in from swfobject but, like you say, usually those vars aren't used instantly in the file and I guess the time it takes to load other assets or run setup functions or whatever must be compensating for IE's slowness.
Thanks for the info - great stuff to be aware of 
This usually works for me:
public function constructor():void { addEventListener(Event.ADDED_TO_STAGE,onAddedToStage); } private function onAddedToStage(e:Event):void { //init()-type stuff goes here }
Originally posted by: JERKSTORE How does IE7 hate SWFObject?
I'm not having any IE7/swfobject problems. I don't exactly know how/why (I have trouble replicating the circumstances), but a lot of times there's some retarded IE error and it goes to a "page not found" page. Remove the SWFObject and the page loads properly.