Embedding Flash content into a web page seems simple and in theory, it is.
But if you’re using embed/object tags alone to embed Flash content, potential issues lurk under the surface.
As Bobby van der Sluis at A List Apart explains, a simple implementation of the embed/object tags alone isn’t perfect.
As per the documentation, SWFObject 2:
- Detects the Flash Player version a user has installed and determines whether to show Flash content or alternative content.
- Doesn’t require vendor-specific markup.
- Implements standards and best practices.
- Can eliminate the “click-to-activate” requirements that some browsers (notably certain versions of Internet Explorer) have due to the Eolas patent.
Will replace the current official Adobe Flash Player Detection Kit in a future version of Flash.
To get started with SWFObject 2:
- Download the code from Google Code.
- Place the SWFObject 2 file in a directory that is accessible by your website’s web pages.
- Decide whether to use the static publishing or dynamic publishing methods that SWFObject 2 offers. The documentation details the advantages of both.
- Follow the instructions on the SWFObject 2 documentation page to embed your Flash content in a web page using the method you’ve chosen.