Closed Bug 301645 Opened 19 years ago Closed 19 years ago

A new version of an extension retains the old options in Extensions dialog

Categories

(Toolkit :: Add-ons Manager, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: pasi.liimatainen, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6

A version of an extension having an optionsURL defined in install.rdf is installed.
A new version of the extension is installed that doesn't have an optionsURL defined.
Firefox doesn't disable the extension's options in the Extensions dialog and
runs whatever used to be in optionsURL when Options is clicked.

Reproducible: Always

Steps to Reproduce:
1. Install an extension with Extensions options defined (such as
http://downloads.mozdev.org/delicious/delicious-0.5.1.xpi)
2. Install the same extension with no Extensions options defined (such as
http://downloads.mozdev.org/delicious/delicious-0.5.6.xpi) while the previous
installation exists
3. Click on the extension's Options in the Extensions dialog
Actual Results:  
After the new version has been installed, Extensions dialog has the extension's
Options enabled even though they should not be. Clicking on the Options button
will run whatever the old version's optionsURL defined.

Expected Results:  
Should have disabled the Extensions menu's options for the installed extension.

Problem exists in Firefox 1.0.6, but not in Deer Park Alpha 2.

It seems the optionsURL is not removed from extensions.rdf even though the new
extension version doesn't declare any options.
(In reply to comment #0)
> Problem exists in Firefox 1.0.6, but not in Deer Park Alpha 2.

That means its been fixed and will be in the next major release of firefox ->
Resolving WFM.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Product: Firefox → Toolkit
You need to log in before you can comment on or make changes to this bug.