238029 - about:plugins display and the translate button (under tools) both cause error reports

Status: RESOLVED EXPIRED

(SeaMonkey :: General, defect)

Description

[crassius]

User-Agent:       Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7b) Gecko/20040316
Build Identifier: Mozilla/5.0 (Windows; U; Win 9x 4.90; en-US; rv:1.7b) Gecko/20040316

about:plugins display and the translate button (under tools) both cause error
reports and yeild incorrect displays

the about:plugins display is truncated before showing any plugins, while the
translate display does nothing at all

about:plugin gives:
Error: uncaught exception: [Exception... "Component returned failure code:
0x8000ffff (NS_ERROR_UNEXPECTED) [nsIStringBundle.GetStringFromName]"  nsresult:
"0x8000ffff (NS_ERROR_UNEXPECTED)"  location: "JS frame ::
jar:resource:///chrome/comm.jar!/content/communicator/plugins.html ::
<TOP_LEVEL> :: line 61"  data: no]

translate gives:
Error: uncaught exception: [Exception... "Component returned failure code:
0x80004005 (NS_ERROR_FAILURE) [nsIPrefBranch.getComplexValue]"  nsresult:
"0x80004005 (NS_ERROR_FAILURE)"  location: "JS frame ::
chrome://navigator/content/navigator.js :: Translate :: line 750"  data: no]


Reproducible: Always
Steps to Reproduce:
1.click about plugins in the help menu or translate in the tools menu
2.
3.

Actual Results:  
error reports and incorrect displays

Expected Results:  
list plugins or translate the current page

Comment 1

[crassius]

still broken in 1.7RC1

Comment 2

[crassius]

still broken in 1.7RC1

Comment 3

[crassius]

still broken in RC2 - errors are the same except that the translate error now
ends as "line 750"  data: no]"

Comment 4

[crassius]

above should have been line 759

Comment 5

[crassius]

errors in 1.7rc3 are still line 61 & line 759

Comment 6

[crassius]

Using 1.7 release the plugin page now works - translate is still broken with
same page 759 error

Comment 7

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

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