I guess it's because AC_OETags.js uses document.write to write the markup straight into a web page, a different strategy.
SWFObject prefers W3C DOM methods over innerHTML and both W3C DOM methods and innerHTML over document.write for various reasons. In general: - W3C DOM methods work for both HTML and XHTML - W3C DOM methods cleanly inserts DOM nodes instead of adding a blob of text or overwrite an existing page - W3C DOM methods can be applied anywhere, e.g. document.write executes where encountered and it cannot inject at a given node point, resulting in scripts in the body of a Web page, and we do *love* unobtrusive scripting :-) - The HTML object element is only partially accessible (and implemented) via W3C DOM methods in Internet Explorer (even in v8), so that's why SWFObject reverts to outerHTML for Internet Explorer For more information on W3C DOM methods vs innerHTML vs document.write please Google the diverse discussions on the Internet. On Jun 10, 12:21 pm, Anton Hughes <[email protected]> wrote: > Hi Bobby > > Thanks for your reply. And yes that does make sense - there are plenty of > "&"s in the data. > > However I am able to pass the JSON data to Flex using Flashvars using Adobes > AC_OETags.js. > > Please see the attached zip for an example. > > Kind regards, > Anton > > JSONdata to FlashVars.zip > 308KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "SWFObject" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/swfobject?hl=en -~----------~----~----~----~------~----~------~--~---
