mozilla
您的搜索结果

    Scripting plugins

    XXX: Dummy p element

    此文档描述了一种新型称作npruntime的跨浏览器扩展,已经在很多组织中用来做开发工作,包括 Mozilla Foundation, Adobe, Apple, Opera, 以及 Sun Microsystems (see press release). 此文档阐述怎样来制作一个可以用脚本调用的插件。

    (A bit of history: NPAPI plugins that used to take advantage of being scriptable via LiveConnect in 4.x Netscape browsers lost this possibility in Mozilla (due to the JNI making the Netscape 4.x JRI obsolete). As an answer to this large gap in the Netscape Plugin API, an extension to the API has been developed that lets plugins be scriptable again, independent of Java. This extension will also let plugins access the script objects in the browser, and is thus a much stronger and more flexible API.)

    The information in this section applies to Firefox 1.0 and Mozilla 1.7.5 and newer versions.

    How the DOM handles scripting

    The Mozilla DOM code now checks if a plugin supports this new scriptability API and if it exposes a scriptable object through this new mechanism. Mozilla does this by calling the old plugin API call with the new enumeration value that has been added to the enumeration.

    The new NPPVariable enumeration is defined in npapi.h as:

    NPPVpluginScriptableNPObject = 15
    

    Threading model

    This API is not designed to be thread safe. The threading model for this API is such that all calls through this API are synchronous and calls from a plugin to methods in this API must come from the thread on which the plugin was initiated, and likewise all calls to methods in this API by the browser are guaranteed to come from the same thread. Future revisions to this API might provide a mechanism for proxying calls from one thread to another to aid in using this API from other threads.

    Security model

    The security model for making calls through this API is much like the general same-origin security model enforced by the browser. That means that script from an origin other than the origin of the page that loaded the plugin is not able to access methods and properties on the plugin. The same thing applies the other way too, the plugin can reach only JavaScript objects in the same origin as the page that loaded the plugin.

    In addition to this, a further extension to this API is being discussed that would give a plugin greater flexibility by letting the plugin control the origin of the calling code, so that the plugin can specify the origin of calls that come from internally loaded code from other origins. This way such code can be executed with only the privileges of the origin of the code, and not the privileges of the plugin page's origin.

    What's in the plugin code?

    A plugin that wishes to be scriptable using this new mechanism needs to return the appropriate NPObject (which is created by calling ) when the browser requests it by calling:

    NPP_GetValue(npp, NPPVpluginScriptableNPObject, ...);
    

    Accessing browser objects from a plugin

    A plugin that wishes to access objects in the browser window that loaded the plugin can do this by getting the NPObject for the browser's window object, or the DOM element that loaded the plugin. This is done by using an extension to . The extensions are two additions to the enumeration, the new enumerations are NPNVWindowNPObject and NPNVPluginElementNPObject. By calling NPN_GetValue() with either of those new enumerations will return an NPObject representing the browser object, and from there, the functions in this API can be used to get and set properties, and to call methods on those browser objects.

    And as always when working with reference counted NPObjects, the caller is responsible for calling on the NPObject to drop the reference.

    The new NPNVariable enumerations are defined in npapi.h as:

    NPNVWindowNPObject = 15,
    NPNVPluginElementNPObject = 16
    

    How to call plugin native methods

    The following HTML code will do the job:

    <embed type="application/plugin-mimetype">
    <script>
      var embed = document.embeds[0];
      embed.nativeMethod();
      alert(embed.nativeProperty);
      embed.nativeProperty.anotherNativeMethod();
    </script>
    

    The API extensions

    The API extensions are based on four new structs:

    文档标签和贡献者

    此页面的贡献者有: ziyunfei, yi_lin, donghao526
    最后编辑者: ziyunfei,