305007 - Themes installer should come built-in with SeaMonkey

Status: RESOLVED INCOMPLETE

(SeaMonkey :: General, enhancement)

Description

[Shriramana Sharma]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050813 SeaMonkey/1.0a
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20050813 SeaMonkey/1.0a

I feel that the themes installer should come built-in with SeaMonkey, just as
Firefox (and Thunderbird) has a built-in themes installer. One should not be
forced to download and install the Themes Installer, then restart Mozilla to get
it activated. It should work right "out of the box".

I searched Bugzilla for theme, themer built-in etc, and didn't find anything so
am filing.

Reproducible: Always

Steps to Reproduce:
1. Install SeaMonkey on a machine which has never had SM before (to exclude the
possibility of a themer.xpi install on a previous Mozilla version carrying over).
2. Search for an option to install downloaded themes.

Actual Results:  
No option to install downloaded themes was seen.

Expected Results:  
It should have provided me with a built-in themes installer.

Comment 1

[zug_treno]

(In reply to comment #0)
> Actual Results:  
> No option to install downloaded themes was seen.

With SeaMonkey 2.0a1pre it is possible to install a theme by dragging the downloaded file to the Add-on Manager.

Comment 2

[Tobias Fischer]

I close this Bug as "Incomplete" for now, but it should be "Invalid", see Bug 342806, hiding of the "Install..." Button affects Theme installing too.

Sad to say that it was intended, that there were no dedicated possibility to install Themes (and other Add-Ons) local after download them to disk. 

Sure installation of any *.xpi including Themes works fine via "File" "Open File..." in Branch and Trunk, also online-installation of Add-Ons and Themes.

In SeaMonkey Trunk you can change the pref "extensions.hideInstallButton" to "false" to make the Install-Button in Add-On-Manager visible for easy Offline-Insallation.

But because it was intended to disable this by default, this Bug was invalid.