STR: 1) Change value of "browser.translation.yandex.apiKeyOverride" parameter to "<Yandex api key>". 2) Change value of "browser.translation.engine" parameter to "yandex". 3) Open some non-english page, e.g. https://de.wikipedia.org/ and click "Translate". 4) "Translating page content…" message is shown, but page is not translated. 5) Change value of "browser.translation.engine" parameter to "Yandex". 6) Open some non-english page, e.g. https://de.wikipedia.org/ and click "Translate". 7) Translated page is shown. IIRC,"browser.translation.engine" has not been case sensitive before, it regressed in Fx 62 or 63. It's quite confusing for users, cause usually values of parameters on about:config is not case sensitive.
Hi there, So the pref was always case sensitive.. What happened is that bug 1488232 changed the expected case for the strings. It went, as you noticed, from "yandex" to "Yandex". The reason was just internal changes. This feature is totally experimental, and we'd never leave this as the main method for people to choose the translation engine.. It would need proper UI in about:preferences that would set the pref correctly. In that case, I don't think it's worth changing the code to make this case insensitive. But I was glad to know that someone is using the yandex engine and it's still working!
Status: NEW → RESOLVED
Last Resolved: 6 months ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.