Well, I'm afraid we still need both methods, because we will not
likely change the functionality of the getFlashPlayerVersion and
hasFlashPlayerVersion methods.

However I am quite positive that for Firefox and Safari (still need to
investigate if this works/how to make it work on other browsers), we
can use the new method to possibly correct corrupt version numbers,
before any DOM related stuff has been decided and executed. So I am
very positive that this will enable us to provide better version
detection in the end. However, version detection results may vary
before the DOM has been loaded and after, which improves the overall
stability of flash version matching, however can cause undesired
results for JavaScript developers...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to