Best that I can tell what happens with onMetadata is that, if (and only if) SWFObject is involved, the first time the event is fired some or all of the metadata may be undefined. The event may be - and often is - called multiple times, and I was putting other setup code in there that I only wanted to activate once the video had started loading. So I put a flag in there to return from the function early if it had already fired and collected the data it needed.
When using just OBJECT embedding, the onMetadata values were always properly set the first time the event fired, so the subsequent event firing were unnecessary duplicates (at least for getting height, width, and duration). But with SWFObject, about 2-5% of the time, the data is undefined the first time the event is fired. This is what it *appears* to be because this bug isn't nearly as reproducible, and it requires a slow connection (I use a laptop connected to WiFi for this), but I'm *hopeful* my code change of allowing onMetadata to refresh itself any arbitrary number of times will work. I'll be re-testing over the next few days. To be safe I'm not allowing the internal vars to be set if the value returned for any metadata is 'undefined'. I'm curious: have you ever seen the Stage sizing bug on any Flash loaded with OBJECT embedding only? Might this be some odd interaction between JavaScript and Flash? --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
