NPAPI plug-in side API

Deprecated
This feature has been removed from the Web standards. Though some browsers may still support it, it is in the process of being dropped. Do not use it in old or new projects. Pages or Web apps using it may break at any time.

This chapter describes methods in the plug-in API that are available from the plug-in object; these allow plug-ins to interact with the browser. The names of all of these methods begin with NPP_ to indicate that they are implemented by the plug-in and called by the browser. For an overview of how these two sides of the plug-in API interact, see the How Plug-ins Work and Overview of Plug-in Structure sections in the introduction.

NPP_Destroy

Deletes a specific instance of a plug-in.

NPP_DestroyStream

Tells the plug-in that a stream is about to be closed or destroyed.

NPP_GetValue

Allows the browser to query the plug-in for information.

NP_GetValue

Allows the browser to query the plug-in for information.

NPP_HandleEvent

Delivers a platform-specific window event to the instance.

NP_Initialize

Provides global initialization for a plug-in.

NPP_New

Creates a new instance of a plug-in.

NPP_NewStream

Notifies a plug-in instance of a new data stream.

NPP_Print

Requests a platform-specific print operation for an embedded or full-screen plug-in.

NPP_SetValue

Implemented by plugins. This call is used to inform plugins of variable information controlled by the browser.

NPP_SetWindow

Tells the plug-in when a window is created, moved, sized, or destroyed.

NP_Shutdown

Provides global deinitialization for a plug-in.

NPP_StreamAsFile

Provides a local file name for the data from a stream.

NPP_URLNotify

Notifies the plug-in instance of the completion of a URL request.

NPP_Write

Delivers data to a plug-in instance. (Remark: Hence the name "NPP_Write" is misleading - just think of:"Data_Arrived")

NPP_WriteReady

Determines maximum number of bytes that the plug-in can consume.

NPAPI plug-in side API

Document Tags and Contributors