|N||myPlugin = navigator.plugins[anIndex]|
|-||myPlugin = myPluginArray[anIndex]|
|HTML syntax:||<APPLET> <EMBED> <OBJECT>|
|Argument list:||anIndex||A reference to an element in a collection|
|Object properties:||description, filename, length, name|
|Object methods:||isActive(), refresh()|
Netscape and MSIE encapsulate plugin/embedded objects in a different way. In MSIE they are objects of the EMBED class. In Netscape Navigator they are objects commonly referred to as belonging to the Plugin class although they are really implemented as JavaObject objects. In MSIE, this is an ActiveX object.
There is additional confusion in that there is a plugins array that belongs to the document and another than belongs to the navigator object. They both contain collections of objects but of different types. This is further confused by the fact that the document.plugins array is another name for the document.embeds array.
Because of this confusing situation the best recommendation is that we refer to document.embeds and navigator.plugins and quietly ignore the document.plugins array. Furthermore we shall refer to Plugin objects as being something the browser can use to play embedded content and Embed objects as instances of a plugin that is alive and running in a document.
Do not confuse Plugin and Embed objects with one another. Plugin objects are owned by the navigator.plugins array. Embed objects are owned by the document.embeds array.