111621 - Profile must contain info about installed APPs (xpi) and URL

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, enhancement)

Description

[Malx]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6+) Gecko/20011121
BuildID:    2001112111

Look at steps.
I thinks is very bad behaior.
IMHO:
 User should get the only message. It must be written in Tab "jabberzilla".
 It must contain:
 "This computer have no JabberZilla component installed"
 Ask admin to do so on this computer (if profile shared for several comp/os)
 Or if you have permission to install
         __click this link__
 "
 <link - is avaliable when user first time installs anything with XPI>

This must be bug/RFE for profile, but also it is XPI bug.

Reproducible: Always
Steps to Reproduce:
1.I have installed JabberZilla.
2.upgrade Mozilla (lost all xpi)
3. get error dialog about "not found .../chrome/packages/jabberzilla.xul
  (it opens on every new mozilla window, while JZ in sidebar)
4. Sidebar tells me "This tab is not avaliable right now".

Comment 1

[Boris Zbarsky [:bzbarsky]]

xp apps

Comment 2

[Peter Trudelle]

->nobody/helpwanted

Comment 3

[Brant Gurganus]

[RFE] is deprecated in favor of severity: enhancement.  They have the same meaning.

Comment 4

[timeless]

.

Comment 5

[Dave Miller [:justdave]]

[e-mail] is about to go on a long vacation to the bit bucket

Comment 6

[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 7

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420