278000 - installing xpi files - incomplete info in help file

Status: RESOLVED INVALID

(SeaMonkey :: Help Documentation, defect)

Description

[kevin]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

The help file already has the following information on installing extensions:

"Getting and Installing Extensions

Installing an extension involves a very similar process to installing themes.
Extensions can be found at Mozilla Update.

There should be an install link for each extension on that extension's page. As
long as JavaScript is not disabled in your browser, clicking this link will
install the extension for you."

Something along the lines of the following could be added:

"Alternatively, an xpi file can be downloaded to your computer. To install the
downloaded xpi file, choose File|Open File in Firefox, browse to the downloaded
file and click open, then click on install now in the dialog box."

Reproducible: Always

Steps to Reproduce:
1. Select Help|Contents
2.Click on Customization|Extensions|Getting and Installing Extensions
3.

Actual Results:  
doesn't explain what to do with an xpi file that is downloaded. Windows doesn't
know automatically.

Expected Results:  
Advise to open xpi from firefox menu (or perhaps .xpi can be associated with
firefox at install?)

Comment 1

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 2

[Ian Neal]

Not for SM2 -> INVALID