SWFObject Interview Questions & Answers

Download PDF

Flash Player's "Settings" panel has a minimum size of 214x137 pixels. If your embedded SWF is smaller than 214x137, Flash Player will not have enough room to display the settings panel, and will make the "Settings..." menu item inactive (grayed out). If you would like the "Settings..." menu item to be clickable, you will need to ensure your SWF is at least 214px wide by 137px tall.

This size constraint also applies to the Express Install dialog.

Recently the team from Anychart.com discovered the reason behind a long standing apparent Flash Player 9/10 memory leak when a user refreshes the page. This bug affects HTML pages which has a swf embedded on the page (whether using SWFObject or not) when viewed in IE 6/7/8. The reason for the bug was actually not the Flash player itself, but the Skype IE plug-in.

This happens when the SWFObject library (versions 2.0 or 2.1) are included more than once on the same web page. To avoid this, make sure that your swfobject.js file is only included once. SWFObject 2.2 will include a fix for this issue.

When you create an iframe on a page that resides on a different domain than the parent page you will get this error which is caused by the Flash plug-in.

When using the dynamic publishing method in Internet Explorer or Firefox on Mac stage.stageWidth and stage.stageHeight might initially return 0 (note that for Internet Explorer the stage size will be available on first load, however when reloading or revisiting a page it will initially be 0).

The solution is to define a resize handler in your ActionScript code. The Flash Player team was obviously aware of this issue and therefore the Flash Player will keep on triggering the stage.resize event until it receives its actual width and height.

An AS3 example:

stage.addEventListener(Event.RESIZE, resizeHandler);
stage.dispatchEvent(new Event(Event.RESIZE)); // force stage resize event for normal cases

function resizeHandler(event:Event):void {
if (stage.stageHeight > 0 && stage.stageWidth > 0) {
stage.removeEventListener(Event.RESIZE, resizeHandler); // only execute once
// your initialization code here
}
}

A new security feature in Flash Player 10 causes SWF's not to be displayed when a HTTP server sends the following response: Content-Disposition: attachment.

The Flash Player version as installed by:

Firefox 3: Type "about:plugins" in the location/address bar and look for the "Shockwave Flash" entry
Safari 3: Click "Help > Installed Plug-ins" in the main menu and look for the "Shockwave Flash" entry

The Flash Player version as detected by:

SWFObject 2
Flash (using HTML `object` element only)
Flash (using HTML `embed` element only)

Flash Player uninstaller
Archived Flash Player versions for testing purposes
The latest released version of Flash Player

When you run an archived Flash Player on Intel-based Macintosh computers please keep in mind that there are two types of Mac installers:

A universal binary installer includes both a version of Flash Player that runs natively on Intel-based Macs and a PowerPC version.
PowerPC installers require browsers to run in Rosetta, which is a special mode that runs older legacy PowerPC applications on Intel-based Macs. You can force a browser to open in Rosetta by opening the info window in Finder (clicking the app and selecting "Get Info"), then ticking the "Open in Rosetta" box. New versions of Safari and Opera no longer support this, but Firefox 3 does.

For static publishing and dynamic publishing you can enable/disable your Flash Player by:

Internet Explorer 7: Menu: Tools > Internet Options, Program Tab, click button: Manage add-on, Filters, Add-ons that run without requiring permission, select Shockwave Object, click Enable/Disable button at bottom, close and restart browser
Firefox 3: Menu: Tools > Add-ons, Plugins tab, Select Shockwave Flash, enable/disable
Safari 3: Menu: Safari > Preferences, Security tab, Web content: check Enable plug-ins
Opera 9.5: Menu: Opera > Quick Preferences > Enable Plug-Ins

For dynamic publishing you can enable/disable JavaScript by:

Internet Explorer 7: Menu: Tools > Internet Options, Security tab, click icon: Internet, click button: Custom Level, scroll to the "Scripting" section of the list, click radio button Disable under Active scripting, close and restart browser
Firefox 3: Menu: Firefox > Preferences, Content tab, Check Enable JavaScript
Safari 3: Menu: Safari > Preferences, Security tab, Web content: check Enable JavaScript
Opera 9.5: Menu: Opera > Quick Preferences > Enable JavaScript

Firefox 3 has a known issue that sometimes causes a swf to be 'double initialized'. The problem appears to be fixed in their codebase, but has not been released yet. See the following bugs for more details: bug 438830 and bug 445599.

Or, if you have "Disable cache" selected in your Firefox Web Developer Toolbar extension a double load will occur.

Firefox 3 on Windows using wmode transparent or opaque introduces a new default style for the object element; it treats it like an active link.

This Firefox implementation deviates from Firefox 3 on Mac, previous Firefox versions on Windows and the default style for the embed element, so it is therefore likely to be a Firefox bug.

The following style rule in the head of your web page should solve this issue:

<style type="text/css" media="screen">
object { outline:none; }
</style>

Do you have the Adblock extension installed? In Firefox 3 Adblock incorrectly blocks Flash content (the object tag only, so that's why content embedded with SWFObject 1.5 does work, because it uses the embed tag), even if your entire page is whitelisted. In this case just disable Flash block (by disabling the extension, don't use Adblock's disable feature, because then it still won't show Flash content). Please note that the development of and support for Adblock has been discontinued.

When using static publishing ensure that you have duplicated your nested param elements for both object elements.

Also the order of certain param elements are important, e.g. the scale parameter should always be declared BEFORE the salign parameter.

The Opera web browser on Nintendo Wii displays both Flash content embedded with static and dynamic publishing. Please note that the Wii currently only supports Flash Player 7 content and that Adobe Express Install is not supported.

The Netfront browser on Sony PSP and older versions of PS3 will only display Flash content when using static publishing. The reason for this is that it's JavaScript support is extremely limited, so that the SWFObject 2 script will never be executed. Please also note that it currently only supports Flash Player 6 content and that Adobe Express Install is not supported.

When using dynamic publishing and a strict HTML DOCTYPE Firefox, Safari and Opera may create a few pixels whitespace underneath your Flash movie.

To avoid this make sure that your object element is set as a block level element, which can be achieved with the following CSS style rule:

<style type="text/css" media="screen">
object { display:block; }
</style>

Special characters and the symbols = and & cannot directly be used inside flashvars values (the latter because they are used to stack the flashvars themselves).

You can workaround this issue by escaping these characters before passing them as flashvar values. An example:

encodeURIComponent("&trade") will become %26trade

The values will be available in your swf already unencoded, so no unescaping is needed inside your swf.

Note that encodeURIComponent is not available in all browsers, but is available in all of the common modern versions. If you need full backwards compatibility, you can use escape() instead, but note that escape() does not work well with double-byte characters (like Chinese).

You can also escape these characters manually by using:

%3D instead of =
%26 instead of &

Microsoft IIS's ASP interpreter incorrectly doesn't allow a page with nested <object> tags, resulting in the following error message:

Active Server Pages error 'ASP 0139'

Nested Object

/yourWebpage.html, line XX

An object tag cannot be placed inside another object tag.

You can avoid this error by using one of the following workarounds (note: which workaround will be best will depend on your specific situation):

Configure IIS not to serve .htm and .html files as ASP
Use a server-side include
Create the object tags dynamically, the 'Update - The Dynamic Approach'

This technote provides additional info and two solutions.

It is preferred to use the first solution that applied to SWFObject 2 embedding looks like the following:

function fixReference() {
window["mySwfId"] = document.forms[0]["mySwfId"];
}
swfobject.addDomLoadEvent(fixReference);

This issue was introduced with the release of Flash Player 9, and is fixed in recent versions of Flash Player 9. You can fix it for the earlier versions by adding the following JavaScript code in the head of your (X)HTML page:

<!--[if IE]>
<script type="text/javascript">
function fixOutOfMemoryError() {
__flash_unloadHandler = function() {};
__flash_savedUnloadHandler = function() {};
}
window.attachEvent("onbeforeunload", fixOutOfMemoryError);
</script>
<![endif]-->

A In order to make fscommand work in Internet Explorer Adobe recommends to add a block of VBScript to capture and forward the FSCommand calls to JavaScript. However VBScript doesn't work anymore when a Flash movie is inserted using innerHTML or outerHTML, as SWFObject's dynamic publishing method does.

Fortunately you can also use JavaScript instead of VBScript to catch the fscommand calls. A small downside is that it uses proprietary attributes (which, again, wrapped in conditional comments will keep your code valid). E.g. the following block of VBScript code:

<SCRIPT LANGUAGE=VBScript>
on error resume next
Sub myCom_FSCommand(ByVal command, ByVal args)
call myCom_DoFSCommand(command, args)
end sub
</SCRIPT>

Can be replaced with:

<!--[if IE]>
<script type="text/javascript" event="FSCommand(command,args)" for="myCom">
myCom_DoFSCommand(command, args);
</script>
<![endif]-->

Including a closing </base> tag will prevent this bug in Internet Explorer being triggered. Because for HTML 4 compliant pages (a closing base tag is forbidden under HTML 4), you could use Internet Explorer conditional comments to keep your HTML valid and still include a closing base tag for HTML 4 documents:

<base href="http://www.yourdomain.com/"><!--[if IE]></base><![endif]-->

In the past years there have been several occasions where a Flash Player didn't expose the right version number externally - as can be retrieved with JavaScript -, caused by corrupt Flash Player Mac OS X installers, affecting Firefox, Opera and Safari on Mac OS X, and also all JavaScript detection scripts, including SWFObject 2, SWFObject 1.5, UFO and the Adobe Flash Player Detection Kit.

Known erroneous versions are (major.minor.release version):

9.0.47 exposes 9.0.19
8.0.24 exposes 8.0.23
9.0.115 exposes either 9.0.47 or 9.0.64 (Note: only Adobe Express Install installers, affecting Firefox on Mac OS X only)

When an install gets corrupted (very often caused by corrupt installers) it is impossible to read the Flash Player version number externally using scripting languages. When using dynamic publishing this results in the display of alternative content, with static publishing we let the object element do its job (it decides whether to show Flash content or alternative content based on its built-in MIME type mechanism) which results in the display of Flash content.

The following technique is also known as Full Browser Flash:

Set both the width and height of your SWF to 100% in your SWFObject definition
Include CSS to get rid of any default margins/padding and set the height of the html element, the body element and the entire chain of block level HTML elements that your SWF will be nested in to 100%, because Firefox (or: any Gecko based browser) in standards compliant mode (or: using a valid DOCTYPE) interprets percentages in a very strict way (to be precise: the percentage of the height of its parent container, which has to be set explicitly):

<style type="text/css" media="screen">
html, body, #containerA, #containerB { height:100%; }
body { margin:0; padding:0; overflow:hidden; }
</style>

Manage the scaling and alignment of your SWF and the positioning of your SWF's elements, within your ActionScript code, e.g.:

stage.scaleMode = StageScaleMode.NO_SCALE;
stage.align = StageAlign.TOP_LEFT;

stage.addEventListener(Event.RESIZE, resizeHandler);

function resizeHandler(event:Event):void {
// center stuff
}

SWFFit (formerly known as FitFlash) is a JavaScript library used to resize Flash movies according to the browser window size, keeping it accessible independent of the screen resolution. SWFFit primarily configures the web browser to display scroll bars when content exceeds the browser window size. It can also be used to dynamically resize the Flash movie size. It is used together with SWFObject.