135705 - refreshPlugins( ) and navigator.plugins.refresh( ) needs to notice new .xpt files

Status: VERIFIED DUPLICATE of bug 154272

(Core :: XPConnect, defect)

Description

[Patrick C. Beard]

The problem, in a nutshell, is that we need to be able to *absolutely guarantee*
the behavior of navigator.plugins.refresh( ) in web delivered JavaScript (and
refreshPlugins( ) in XPInstall) to cause new interfaces in xpti.dat to become
available immediately.  It seems that it is possible to run
navigator.plugins.refresh( ), refresh xpti.dat, and still not have the inteface
for use immediately.  Is there some RAM-caching of the "older" xpti.dat
contents?  Is there something we can do to force compliance?

Comment 1

[Patrick C. Beard]

Attachment: autoreg.html

This script, which can only be run locally, does autoregistration.

Comment 2

[John Bandhauer]

Except for the recent bug *fix* where navigator.plugins.refresh was made to not
autoreg xpcom if the plugin on the page has not changed, I know of no reason why
new xpt files would not be found and their interfaces not discovered and made
available for use. Do you have a testcase?

Comment 3

[Arun Ranganathan]

Changing the summary to suggest that XPI's refreshPlugins() and 
navigator.plugins.refresh() should do the same thing, namely, if XPT is 
installed in Components, make it available in the infrastructure immediately 
after refreshPlugins( ) invocation.
Now: I've got a test case of this problem in Bugscape 13751 
(http://bugscape.netscape.com/show_bug.cgi?id=13751).  I'm sorry it's in 
Bugscape, but I'm using third party software in my XPInstall package and until 
I get permission, I don't want to post it outside the firewall.

Comment 4

[Peter Lubczynski]

Not sure if this is a dup of bug 154272 or going to be WFM because the code now
supports explicity calling XPCOM autoregistration on plugins.refresh(), even if
plugins have not changed. See:
http://lxr.mozilla.org/mozilla/source/dom/src/base/nsPluginArray.cpp#184

I think it's the same thing the attachment does, except without security warnings.

That's XPCOM autoregister but I think plugins are more interested in just
refreshing xpti.dat which bug 154272 will fix refreshing whenever plugins have
'changed'.

Comment 5

[Peter Lubczynski]

*** This bug has been marked as a duplicate of 154272 ***

Comment 6

[Phil Schwartau]

Marking Verified -