292927 - "Restart to Complete" behavior is broken - mime type forever cached

Status: RESOLVED EXPIRED

(Firefox :: Installer, defect)

Description

[Michael Scholz]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

If my plugin installs via the xpi installer technique; the situation of plugin
in memory is handled by renaming the old plugin and telling the end user to
restart their browser. "Download Failed: Restart to Complete". When the end user
restarts their browser, the new plugin replaces the old plugin. But the mime
type of the plugin remains the same as the previous version of the plugin. When
this situation occurs, no amount of restarting will ever update the Mimetype to
the correct values. This is a bug in Netscape 7.2 and Firefox 1.0.3

Reproducible: Always

Steps to Reproduce:
1. Make a plugin with a mimetype
2. Make a new version of the plugin, with a different mimetype
3. Install the plugin version 1
4. Browse a page that embeds the plugin, thus loading it into memory
5. Browse a page that xpi updates the browser plugin to version 2
6. Witness the error message "Restart to Complete"
7. Restart browser
8. Note that about:plugins shows the version 1 info, even though version 2 is
now installed. 

Actual Results:  
about:plugins shows the version 1 info, even though version 2 is now installed. 


Expected Results:  
Refreshed the registered mimetype to match the new plugin dll. 

I think this is serious, so I marked it major. No one uses xpi installer for
plugins, bugs like this make it obvious why.

Comment 1

[Gervase Markham [:gerv]]

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/

Comment 2

[Gervase Markham [:gerv]]

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.