Closed Bug 271675 Opened 20 years ago Closed 19 years ago

Translate Page option on tools menu does not work on certain websites

Categories

(SeaMonkey :: General, defect)

1.7 Branch
x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: mikulmakim, Unassigned)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040616

On www.humour.com when you try to use 'Translate Page' option, it will not do
anything.  In this case I had to go to Google and translate from French to
English from there.

Reproducible: Always
Steps to Reproduce:
1.Go to www.humour.com
2.On the main page or any other page go to the Tools Menu and Select Translate Page


Actual Results:  
There was no activity at all, not even an error message

Expected Results:  
It should have translated the page from French To English through Google
language tools.

I am using the modern theme
The problem has occured on other websites as well
Just tested the bug with default(classic) theme and it sitll has the same results.
The 'Translate Page' command dosen't work
In my case it doesn't depend on the site: it's never worked. This is the
javascript error I get:

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 771"  data: no]


Mozilla 1.7.5 / Windows XP Professional SP2
Same here. This ounds like a duplicate bug. See
https://bugzilla.mozilla.org/show_bug.cgi?id=238107 (older).
Version: unspecified → 1.7 Branch
See bug 296844 for possible cause.
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.