Bug 44351

Summary: NPAPI plugins do not get instantiated when not in visible pages
Product: WebKit Reporter: Phil <phil.ames@gmail.com>
Component: Plug-insAssignee: Nobody <webkit-unassigned@lists.webkit.org>
Status: UNCONFIRMED    
Severity: Normal CC: ap@webkit.org
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Mac OS X 10.5   
Bug Depends on:    
Bug Blocks: 56575    
Attachments:
Description Flags
Plugin and sample HTML pages. none

Description From 2010-08-20 13:26:31 PST
Hi,
I have a scriptable NPAPI plugin that I would like to reside in the 'global.html' page of a Safari extension.  My global.html contains a tag such as:

<object type="application/basic-plugin" id="foo"></object>

Periodically, the global HTML page will need to call something like:

var plugin = document.getElementById('foo');
var rv = plugin.bar();
// perform some computation with rv

If I put this in a regular HTML page, this works fine.  If I place it in a standard iframe, it also works fine.  If I place this code in an iframe such as:

<iframe src="inner.html" style="display:none;">

or in the global.html page of a Safari extension(which is also hidden), the scriptable plugin is never instantiated and all calls to methods in it fail with the following exception:

TypeError: Result of expression 'document.getElementById('foo').bar' [undefined] is not a function

I have attached to this bug a non-scriptable NPAPI plugin that simply logs to stderr when NPP_New() is invoked.  After compiling the plugin, you will need to install it by placing build/Debug/BasicPlugin.bundle/ in ~/Library/Internet Plug-Ins/.  Then, launch Console.app (to observe stderr logs) and navigate to the included outer.html.  Note that nothing is printed to stderr.  Then, navigate to inner.html and observe the log to stderr about NPP_New() being invoked.

The code is based on sample code provided by Mozilla: http://mxr.mozilla.org/mozilla-central/source/modules/plugin/sdk/samples/basic/mac/

The code *does* work on another Webkit-based browser (Chrome) so this may not be a Webkit-specific problem, but there does not appear to be a public Safari bug tracker.
------- Comment #1 From 2010-08-20 13:27:15 PST -------
Created an attachment (id=64982) [details]
Plugin and sample HTML pages.