On Oct 22 2010, 7:12 pm, Aran Rhee <[email protected]> wrote: > so what you are saying is correct in that the "success" swfobject is > measuring if the minimum flash player was available and if the <object> dom > element which was made for the swf was actually created and available. As > far as successful embedding goes, this is all that is required.
I got hung up on this myself. I realize this is an old thread, but the docs still haven't been updated to clarify what the callback function *really* is doing, so it's worth revisiting. Suppose you did a survey of Flash developers and asked them "You are using SWFObject to put a SWF on a page, and a user visits the page. For that user, the SWF fails to download successfully. Has the SWF been embedded successfully or not?" What do you think the consensus would be? Obviously it would be "no, it was unsuccessful." Think about the plain sense of the phrase "embedded successfully." It's not successful if it doesn't download! To say otherwise would be like saying a car runs successfully because the starter motor turns over-- even if the engine itself won't start. The documentation should be written so that it is clear and plain, and not depend on readers to comprehend technical subtleties like "the SWF file can be blocked or missing but we will still consider it embedded successfully because that's how we define 'embedded'." If the best we can do in the callback function is report if the min Flash player is available and that the <object> dom element for the SWF was created, that's what the docs should say. -Josh -- 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.
