Closed Bug 1579740 Opened 6 years ago Closed 6 years ago

translate webcontent does not work

Categories

(Firefox :: Translations, defect)

Product:
Firefox
Component:
Translations
Version:
71 Branch
Platform:
x86_64
Windows 10
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED INVALID
Tracking Flags:
Tracking Status
firefox71 --- affected

People

(Reporter: vtol, Unassigned)

Details

  • W10 Pro x_64 v1903 b18362.295

maiden profiles of:

  • FX 71 b 171d5f099ad0d22feda354c74182703ed02842a7

  • FX 70 b 5da3c0a0771e9c2ff102bfc5d97d9bb5bb93788e

  • FX 69 b cce4622026ab8e0130a0afc03f829f9b19ca38c2

  • browser.translation.detectLanguage true

  • browser.translation.engine Bing (or other translation engine)

  • browser.translation.neverForLanguages

  • browser.translation.ui.show true

  • browser.translation.ui.welcomeMessageShown true

  • reference url https://www.20minutes.fr (but happens on other domains as well)

each browser instance displays the UI notification but when pressing Translate | Try Again each results in:

There has been an error in translating this page

Error console only printing:

uncaught exception: failure

Has the underlying code/api for processing the translation been removed from FX and the UI is just a left over?

The priority flag is not set for this bug.
:florian, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(florian)

(In reply to vtol from comment #0)

Has the underlying code/api for processing the translation been removed from FX and the UI is just a left over?

The API key has never been built in. We don't have a key that would support enough translation volume to include it in Firefox.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Flags: needinfo?(florian)
Resolution: --- → INVALID

Unless I am mistaken it used to work in some previous FX version, not sure though which been the last one.

What is the purpose then of governing settings and UI code, would seem like garbage in the FX code base being carried around for no reason? Notwithstanding, letting Chrome based browsers having an usability advantage.

It never worked without creating yourself the preference containing your own API key. This code is there so that we can run studies on a few users to see how much the feature gets used when we provide it.

Reading https://wiki.mozilla.org/QA/Translation and https://support.mozilla.org/en-US/kb/automatic-translation the last test seems ages ago, Nightly 36... The cited Bing api key not working any more.

And the cited meta bugs would appear all but abonded.

The settings for the api keys for the various translation engines are not well documents either, one would have to dig into other source than Moz to find something about it.

The Bing code is obsolete (the server APIs have changed). The most recently touched translation engine is Google.

You need to log in before you can comment on or make changes to this bug.