266336 - Needed: more information in chrome error messages

Status: RESOLVED EXPIRED

(Thunderbird :: Mail Window Front End, defect)

Description

[David A. Cobb]

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

Using the Sunday build (10/24) with a boatload of Extensions . . .
At least one extension is not good; however, from the information shown in the
message we will never never know which one!  My 'puter can't find the key words
in any .XUL -- probably because it's too dumb to unzip them and look inside.  

Anyway, PLEASE put into the error box: filename, and if possible line-number and
whatever else might help diagnose a chrome/xul error.
Also, The arrow ------^ is very nice, but there's no easy way to know what might
be wrong at that point.  Unknown attribute?  Invalid value?  Something else?

While you're at it, it would be nice if the error panel were in a separate
window so it didn't tie up display space in the 3-pane.

NOTE: I add this because anything I put up that involves extensions gets shot
down lately.  I am NOT reporting the bug that exists in some extension's chrome!
 I am reporting the bug in the basic handler that doesn't issue good error
displays.  

Reproducible: Always
Steps to Reproduce:
1. Run Thunderbird


Actual Results:  
The three-pane display is as shown on the attachment.

Expected Results:  
The error display panel should provide sufficient information to indicate what
extension (if any, of course) is involved - what file should be fixed or removed
-- etc.

Comment 1

[David A. Cobb]

Attachment: Screenshot (png) showing useless error display

You may need to scale it up a bit to make it legible.

Comment 2

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

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