Specifications

CHAPTER 16
318
<noscript> block The code in the <noscript> block uses <object> and <embed> tags to embed the SWF file in
the HTML page for users who have disabled JavaScript in their browser. The
<noscript> block is useful if your
application requires JavaScript (for example, if you use the ExternalInterface API in your application). You can use
this block to warn users that they will have limited functionality, or redirect them to another site. For a simple
application, however, your
<noscript> block typically contains identical tags as they are defined in the JavaScript
file. For more complex wrappers that include support for Express Install, the
<script> block can include a
considerable amount of JavaScript code.
About the JavaScript file
The JavaScript file consists of a set of document.write() methods that write the <object> and <embed> tags
that embed your application. In this example, these tags are identical to the
<object> and <embed> tags used in
the HTML page’s
<noscript> block. In more complex configurations, you can add Express Install or deep linking
support to the JavaScript file that is not supported in the HTML page’s
<noscript> block. Remember that the
code in the HTML page is for browsers that do not support JavaScript.
The <object> tag’s codebase and the <embed> tag’s pluginspage properties add support for basic player version
detection and installation. The
codebase tag defines the minimum version required at the end of the URL (for
example,
#version=9,0,0,0). If a client requests this page with a player version older than the version specified,
they are prompted to upgrade their player.
The upgrade experience is considerably better with Express Install. If the user’s player does not meet the minimum
requirements, the new player is automatically installed for them. You add Express Install by editing your wrapper.
For more information, see “Using Express Install” on page 333.
With a generic wrapper, a user who clicks the Back and Forward buttons in their browser navigates the HTML
pages in the browser’s history and not the history of their interactions within the Flex application. Deep linking
lets users navigate their interactions with the Flex application by using the Back and Forward buttons in their
browser. You can add deep linking by editing your wrapper. For more information, see “Deep Linking” on
page 1065 in Adobe Flex 3 Developer Guide.
In addition to adding deep linking and Adobe® Flash® Player detection support to your wrapper, you can use other
properties of the
<object> and <embed> tags to add functionality. For more information, see “Ab o u t t h e o b j e c t
and embed tags” on page 321.