<div id="readability-page-1" class="page"><div data-astro-cid-57z6rh23=""><hr>
Ran into a problem where <code>ExternalInterface.call()</code> in Flash only misbehaves in Internet Explorer.
The code is simple:
<pre tabindex="0" data-language="actionscript-3"><code>ExternalInterface.call("document.location.href.toString")</code></pre>
It works fine in Firefox, but Internet Explorer doesn’t return the value properly.
It doesn’t work when the swf is embedded with an html <code>object</code> tag. The cause is that the object had no <code>id</code>.
<blockquote>
<h2 id="external-api-requirements-and-benefits">External API requirements and benefits</h2>
The External API is part of ActionScript. It provides a communication mechanism between ActionScript and the code running in the “external application” that hosts Flash Player as a container — typically a web browser or a standalone projector application. In ActionScript 3.0, the External API’s functionality is provided by the ExternalInterface class. In versions before Flash Player 8, the <code>fscommand()</code> action was used to communicate with the container application. Starting with Flash Player 8, the ExternalInterface class replaces <code>fscommand()</code>, so it’s recommended for all communication between JavaScript and ActionScript.
The ExternalInterface class is a subsystem that lets ActionScript and Flash Player communicate easily with JavaScript on an HTML page, or with a desktop application that embeds a Flash Player instance.
The ExternalInterface class can only be used in the following cases:
<ul>
<li>Any supported version of Internet Explorer for Windows (5.0 or later)</li>
<li>A container application, such as a desktop application, using an instance of the Flash Player ActiveX control</li>
<li>A browser that supports the NPRuntime interface, currently including:
<ul>
<li>Firefox 1.0 or later</li>
<li>Mozilla 1.7.5 or later</li>
<li>Netscape 8.0 or later</li>
<li>Safari 1.3 or later</li>
</ul>
</li>
</ul>
In every other case (e.g. running in a standalone player), the <code>ExternalInterface.available</code> property returns <code>false</code>.
ActionScript can call JavaScript functions on an HTML page. Compared to <code>fscommand()</code>, the External API offers these improvements:
<ul>
<li>You can call any JavaScript function, not just the ones used with <code>fscommand()</code>.</li>
<li>You can pass any number of arguments with any name — no longer limited to a single command plus a single string argument, so it’s far more flexible than <code>fscommand()</code>.</li>
<li>You can pass different data types — Boolean, Number, String — no longer limited to String parameters.</li>
<li>You can receive the return value of the call, and it’s returned to ActionScript immediately as the result of the call.</li>
</ul>
</blockquote></div></div>

oeoe.io · Articles

Jeong-Un, Kim

--- Ran into a problem where ExternalInterface.call() in Flash only misbehaves in Internet Explorer. The code is simple: It works fine in Firefox, but…

Flash's ExternalInterface.call() Doesn't Work in Internet Explorer

댓글