The tracking of replaced/altertnative content in memory

[GoogleCodeExporter]

It could be extremely beneficial in the case where Flash content is
replacing HTML content, if the content which was replaced was stored in
memory and accessible via the SWFObject API. This could make creating Flash
menus, buttons, content etc which can gracefully degrade for those without
the player to view the HTML equivalent of the Flash. Also allowing the
Flash author to create dynamically built Flash text in
menus/buttons/content to match the HTML. This would make updating Flash as
easy as simply updating the HTML.

Original issue reported on code.google.com by andrewi...@gmail.com on 4 Mar 2009 at 10:21

[GoogleCodeExporter]

meant for that to be an enhancement

Original comment by andrewi...@gmail.com on 4 Mar 2009 at 10:21

[GoogleCodeExporter]

Original comment by bobbyvandersluis on 5 Mar 2009 at 12:43

• Changed state: Accepted
• Added labels: Type-Enhancement
• Removed labels: Type-Defect

[GoogleCodeExporter]

Original comment by bobbyvandersluis on 1 Apr 2009 at 10:00

• Changed state: OnHold

[GoogleCodeExporter]

The current API is flexible enough to help you make HTML and SWF pages like 
this.
Making shortcut methods is out of scope.

Original comment by bobbyvandersluis on 28 May 2009 at 8:03

• Changed state: WontFix