Closed
Bug 396994
Opened 18 years ago
Closed 17 years ago
Chrome Registration error message does not name the failing extension
Categories
(Toolkit :: Add-ons Manager, defect)
Tracking
()
RESOLVED
DUPLICATE
of bug 302527
People
(Reporter: rbgray, Unassigned)
Details
Attachments
(1 file)
|
24.48 KB,
image/png
|
Details |
Build identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US;
rv:1.9a8pre) Gecko/2007090801 SeaMonkey/2.0a1pre
When a faulty extension causes a Chrome Registration error, the
error dialogue says:
Chrome Registration Failed
SeaMonkey could not install this item because of a
failure in Chrome Registration. Please contact the author
about this problem.
Unfortunately, this message does not indicate the identity of the failing extension, making diagnosing the problem more difficult. Users are likely to consider the author to be the authors, resulting in misdirected support requests. By incorporating the extension name into this dialogue, the problem can be more quickly diagnosed.
Reproducable: always*
Steps to reproduce:
1. start SeaMonkey with a faulty extension
Expected results:
The Chrome Registration error dialogue should name the failing extension. (For extra credit, if there is additional info that can be retrieved from the extension, such as a support address, it should also be displayed.)
Actual results:
The text above (and screenshot) is displayed.
* I was last able to reproduce this with the SeaMonkey trunk builds in early
September which suffered a crash when run for the first time with no write
access to the .app file. see
https://bugzilla.mozilla.org/show_bug.cgi?id=371298#c25 . The resolution of Bug
392475 fixed this crash scenario.
| Reporter | ||
Comment 1•18 years ago
|
||
Sorry, hit Submit prematurely. Meant to say "Users are likely to
consider the author to be the main product (SM/FF/TB) authors, ..."
Comment 2•17 years ago
|
||
Is this a dupe of bug 302527?
Updated•17 years ago
|
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → DUPLICATE
| Assignee | ||
Updated•17 years ago
|
Product: Firefox → Toolkit
You need to log in
before you can comment on or make changes to this bug.
Description
•