NPAPI also supports scripting, printing, full-screen plugins, windowless plugins and content streaming. NPAPI requires each plugin to implement and expose approximately 15 functions for initializing, creating, deleting and positioning plugin content. The plugin runs in-place within the page, as opposed to older browsers that had to launch an external application to handle unknown content types. The plugin is responsible for rendering the data. When the browser encounters a content type it cannot handle natively, it loads the appropriate plugin, sets aside space within the browser context for the plugin to render and then streams data to it. In NPAPI architecture, a plugin declares content types (e.g. Initially developed for Netscape browsers, starting in 1995 with Netscape Navigator 2.0, it was subsequently adopted by other browsers. Netscape Plugin Application Programming Interface ( NPAPI) was an application programming interface (API) of the web browsers that allows plugins to be integrated.

Java browser with flash player