226053 - xptpath specifying scripting capabilities for a plugin ignored in the windows registry

Status: RESOLVED WONTFIX

(Core Graveyard :: Plug-ins, defect)

Description

[~Happy Dude~]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5) Gecko/20031007 Firebird/0.7

According to documentation here:

http://www.mozilla.org/projects/plugins/first-install-problem.html

A plugin may create entries for itself in the windows registry to identify
itself to all existing and all future installed versions of mozilla.  A part of
what a plugin may identify about itself in the registry is the path to an xpt
file for the plugin that defines the scriptability of the plugin.  This
information is supposed to be saved in a registry value named 'XPTPath'.

As far as I can tell, the browser is failing to read and react to the data
stored in the 'XPTPath' registry value.

Reproducible: Always

Steps to Reproduce:
1.Obtain a plugin for mozilla in windows that is scriptable (has an associated
XPT file).
2.Create an appropriate PLID key for that plugin in the windows registry, and
include an 'XPTPath' value according to the documentation at
http://www.mozilla.org/projects/plugins/first-install-problem.html.
3.Start up a browser that would otherwise be unaware of the plugin just
registered, and view a page that contains content for the plugin.

Actual Results:  
Notice that the browser successfully identifies and makes use of the plugin, but
ignores the XPT and associated scriptability of the plugin.

Expected Results:  
The browser should identify and use the plugin, AND identify and use the
associated XPT file to allow scriptability of the plugin.

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.

Comment 3

[Ivan Pool]

I experience the same problem in the following recent versions of Mozilla browsers:
* Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.11) Gecko/20050728
* Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.10) Gecko/20050716 Firefox/1.0.6
The only workaround is to install the plugin in the installation directories of the browsers. This means that future installed Mozilla browsers are not able to use the plugin, which is quite annoying.
The description below contains all the information required to reproduce the problem.

Regards,
Ivan.

Comment 4

[Robert Strong (they/them - no direct email)]

Reference http://developer.mozilla.org/en/docs/Plugins:_The_First_Install_Problem#Proposed_Solution

Comment 5

[Robert Strong (they/them - no direct email)]

Since we no longer support XPTPath on trunk resolving -> wontfix per jst