XPInstall: refreshPlugins not working in install.js

RESOLVED EXPIRED

Status

RESOLVED EXPIRED
14 years ago
3 years ago

People

(Reporter: bugzilla, Unassigned)

Tracking

Trunk
x86
Windows 2000

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.8) Gecko/20050511 Firefox/1.0.4

Hello,

I'm trying to install a plugin in firefox. This plugin is unknown to the plugin
finder service.

The problem is, that calling refreshPlugins(true) in install.js doesn't work in
Firefox 1.0.4, but in Mozilla 1.7. The plugin is not redrawn. You need to reload
the page manually. And after reloading the page manually, the yellow information
bar is still shown and tells that there are additional plugins required.

code fom install.js:

errorCode = performInstall();
if (errorCode == SUCCESS) {
  alert("refresh");
  refreshPlugins(true); 
}


Reproducible: Always

Steps to Reproduce:

Actual Results:  
The plugin is not shown after installing. You have to reload the page manually,
but there's no hint to do so.

Expected Results:  
refreshPlugin(true) should reload the page automatically after installing the
plugin.
(Reporter)

Updated

14 years ago
Component: Plugin Finder Service → Extension/Theme Manager
Summary: XPInstall: refreshPlugins not working in install.js → XPInstall: refreshPlugins not working in install.js
Do you also have an install.rdf? If so, the install.js will not be read.
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> Do you also have an install.rdf? If so, the install.js will not be read.

No, I don't. I have only an install.js.
Component: Extension/Theme Manager → Installer: XPInstall Engine
Product: Firefox → Core
Version: unspecified → Trunk
This also affects seamonkey trunk.
Assignee: nobody → xpi-engine
QA Contact: plugin.finder
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.