Well, lets take a step back. IIRC, the code generator, while it generates the proper syntax it does generate script inline, which we've already established that, in FF3.5 causes issues that we don't see anywhere else. While we'd like to put things in the <HEAD> area of your HTML doc, we've also established that you can't do that due to access reasons.
So... Could you please paste the code and/or supply a link to the page that has the code that you generated for your situation. Identify the code as "Used code generator" and let's confirm that the only place that this doesn't work for you is FF3.5? Because SWFObject works. I guarantee it, so there's either something in the way your coding, or some related issue on your web page or your browser testing environment that is causing mishaps. My initial take will be to look at your code generated code, and then show you what specifically to wrap in your domready event. I will even be happy to do a view source and troubleshoot locally until I can get things working. As far as using createSWF vs. embedSWF. I'm hesitant to agree with Kyle on this point only because I don't know off the top of my head if there needs to be any kind of encoding or special ways of generate the params object when you also include flashvars. I like the method exposed that allows you to define flashvars in Javascript Object Notation (JSON), and enjoy that comfort. However, I also acknowledge that Kyle might have insight into the issue that I don't. But I would prefer not to mix and match methods as it will confuse the issue. Create a page with the code generated from the generator. Lets look at it, discuss. I expect this will only take 1-2 rounds of discussion before we get it right. Vincent On Thu, Jul 23, 2009 at 8:23 AM, citznfish <[email protected]> wrote: > > > > On Jul 22, 4:29 pm, Vincent Polite <[email protected]> > wrote: > > I suspect the way you are defining your flashvars as a parameter > attribute > > is munged. Which is why I would use the embedSWF method and build your > > attributes, parameters, and flashvars as single - level object/arrays > > instead of doing the nested name value thing in the parameters > collection. > > > > Unfortunately I have a meeting to head to, so I won't be able to take a > look > > at this further. I would strongly suggest you go back to the code > > generator. Generate the code there for the specific variables you are > > interested in. The Dynamic publishing method already handles the whole > > "make sure you have version X of Flash movie" for you. > > > > The only difference between the code generator and what you will want to > put > > in your page because you can't put things in the <head> portion of the > page, > > would be to set up your calls inside your SWFLoad function which should > just > > be a straight call to define the parameters and embed the Flash object > with > > a minimum standard for Flash defined in the embedSWF method. > > > > VP. > > > I had tried the code generator as well and had the same issues with > FF. I'm not sure what else we can do... > > > --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
