Did you read the old docs on ExternalInterface.objectID? It still states it returns the "id" for IE (InstallAX.exe) object or the "name" of a Netscape embed (InstallPlugin.exe). Now, it does say Netscape which is amusing but it could still be true. I have my documentation filters up to version 11.8 and it still states it:
Language Version: ActionScript 3.0 Runtime Versions: AIR 1.0, Flash Player 9, Flash Lite 4
Returns the id attribute of the object tag in Internet Explorer, or the name attribute of the embed tag in Netscape.
It's anyone's guess if this is still the case.
Yes, I read that documentation a long time ago, and that's what I suspected, but...
The problem is that both of these plugins are running in the same browser (Chrome), yet one uses "name" while the other uses "id".
Since Chrome's plugin was using "id", one would expect the debug version of the player in that same browser to use the same "id" attribute. Instead, the behavior is inconsistent in the same browser.
I'm surprised swfobject doesn't include "name" by default, given the history of the different plugin versions.
The built-in player says the plugin type is: "PPAPI (out-of-process)" (Pepper Plugin API) while the debug player has type "NPAPI" (NetScape Plugin API). The Pepper Plugin API must use the "id" attribute while the NetScape API still uses the "name" attribute. Adobe should probably update the docs to account for this new "Pepper" API and say it uses the "id" attribute as well, and may want to mention that Chome uses a different API for the debug player.
1 person found this helpful
I expect Firefox would also indicate NetScape Plugin API as well. In this case it appears their docs are already up to date though, although using "Netscape" does add a layer of dust to it.
Hopefully you can just add the name to swfobject and don't have to many separate objects so it's not that big of a deal in the end.