Firefox 70 disable this extension

[simonbcn]

Firefox 70.0.1
Google Translate this page 2.3.1

Firefox disables this addon because: https://blocked.cdn.mozilla.net/11fd123a-e67d-44ab-909f-b776ea2e8d0a.html Any workaround?

[Onurtag]

Yeah that link tells the story. https://bugzilla.mozilla.org/show_bug.cgi?id=1593243

A workaround is modifying the manifest.json and signing it yourself but why do we have to go that far for an addon that isn't on amo.

They killed every single translation addon that doesn't compromise to be on amo. They shouldn't have done this before releasing their own translation service.

[andreicristianpetcu]

I had a few email exchanges with amo reviewers. It's sad that we cannot use this extension without hacks.

On the bright side there will be less malware shipped trough extensions. Believe me, there are lots of such cases. I will post more details about my interaction with them. It's not an ideal situation but I understand their point of view.

[N-X-T]

:((

[haselwarter]

This is kind of a big deal for a lot of people who need to regularly translate pages in Firefox. I have to switch to Chrome for these pages now. Is there an issue on foreign language support for Firefox anywhere?

[dessant]

A workaround is modifying the manifest.json and signing it yourself but why do we have to go that far for an addon that isn't on amo.

That's not a solution, Mozilla does not allow you to run a perfectly safe extension such as Google Translate This in the release version of Firefox, even if it is not listed on Firefox Add-ons, and even if you sign it for personal use only. They still control a signed extension and will blocklist it the same way.

See also what happened with Page Translator: https://github.com/jeremiahlee/page-translator/issues/26

[simonbcn]

I've changed to Page Translator Revised, it works very similar to this.

[grahamperrin]

Nit: blocks such as this are not specific to Firefox.

The block is equally effective in Waterfox Classic, and so on.

… Is there an issue on foreign language support for Firefox anywhere?

The sad state of language translation in Firefox ▶ Firefox is getting language translation and it's safer than Google Chrome's | Trusted Reviews ▶

• Bergamot

[dessant]

@grahamperrin, is Waterfox planning to override the blocklist for these two extensions? I think not participating in this security theater would be a great differentiator for the Waterfox project.

[jscher2000]

Userscript hosting extensions can still do what the content script needs to do. I think they cannot prevent that because there's no code review of userscripts. Therefore:

https://greasyfork.org/en/scripts/391935-inject-google-translate-widget

Edit: As noted in a later reply, some pages' CSP rules will prevent the remote script injection.

[grahamperrin]

@dessant https://github.com/jeremiahlee/page-translator/issues/26#issuecomment-545636643

[grahamperrin]

https://github.com/andreicristianpetcu/google_translate_this/issues/19#issuecomment-549180326

🥇

https://www.42.fr/ par exemple:

Also tested with https://www.geekfaeries.fr/ et des autres.

[dessant]

@grahamperrin, I agree that disabling blocklisting in the browser is a bad idea, I was asking if Waterfox maintainers would consider overriding the block for these two specific extensions, since they're safe to use, and offer a better user experience than an user script.

[sprite-1]

@jscher2000 can you make it so that calling the function automatically loads the translation instead of having to do another click to translate?

[andreicristianpetcu]

@jscher2000 The user script will not work on sites with CSP such as GitHub. You can try to disable CSP with this extension and then run the user script https://addons.mozilla.org/en-US/firefox/addon/laboratory-by-mozilla/

Disabling CSP for every site is NOT a good idea and this extension gives a bit more control. I did a lot of fancy stuff to inject new CSP rules in my extension.

[jscher2000]

@jscher2000 can you make it so that calling the function automatically loads the translation instead of having to do another click to translate?

If you change autoDisplay: true to autoDisplay: false on line 21, it seems Google will translate automatically, but I haven't tested it much.

[jscher2000]

@jscher2000 The user script will not work on sites with CSP such as GitHub. You can try to disable CSP with this extension and then run the user script https://addons.mozilla.org/en-US/firefox/addon/laboratory-by-mozilla/

Yes, this is a limitation, but the best approach to solving it is not clear. Users often have at least one extension modifying CSP (such as uBlock Origin) so it can be unpredictable adding a new one to the mix. Still not solved: https://bugzilla.mozilla.org/show_bug.cgi?id=1421725

[grahamperrin]

@dessant I think, raise the Waterfox question in the Waterfox support area.

https://redd.it/dl42c9 will be ideal, do you have a Reddit account?

Defocusing from Waterfox …

---

… I think not participating in this security theater would be a great differentiator …

Any browser/project that begins selectively picking holes in a primary blocklist – setting the precedent for any number of future hole-picking dramas – might be perceived as engaging in theatrics.

Re: https://www.jeremiahlee.com/posts/page-translator-is-dead/ "… Nuance should not be dead. …" – true, but not everyone will appreciate nuances.

HTH

[ostrolucky]

This extension can't be installed on Firefox developer edition either. Is there any instructions available how to install it in Firefox >= 70?

[11sideways]

checked - FF 52, 55, 56, 57, 58, 60, 65, 67, 68, 69 (and all other i think) blocks this extension after 5 minuts good works, altrough i started cleared FF and disable updates+sharing stats all times. If somebody can... Please, tell me (us) step by step, how to disable checking addons, or any solution for make this addon works.

[bhaskoro-muthohar]

So there is still no fix onto this issue?

[sprite-1]

@bhaskoro-muthohar there s nothing to fix. Mozilla decided they don't like the addon and blocked it.

[bhaskoro-muthohar]

@bhaskoro-muthohar there s nothing to fix. Mozilla decided they don't like the addon and blocked it.

suck. They forced us to migrate to other browsers. Do you guys have alternative add-on or migrated to chrome?

[sprite-1]

@bhaskoro-muthohar I just disabled the blocklist to continue using. It's not recommended if you have a habit of downloading new addons every time due t security but for me, I only use a few specific addons so I don't have an issue disabling it.

[ostrolucky]

Well workarounds such as disabling blocklist was what we ask for. There is literally no instructions how to workaround the limitation. We are asking what we need to change in firefox settings or files, or anything else to continue using the browser and extension. Can you share with us how did you disable the blocklist?

[sprite-1]

Just go to about:config and look for extensions.blocklist.enabled then set it to false

[grahamperrin]

… extensions.blocklist.enabled then set it to false

Please don't promote this without also making the risks unmistakably clear.

See https://github.com/jeremiahlee/page-translator/issues/26#issuecomment-550173251 – more to add, there, in a few minutes.

[sprite-1]

@grahamperrin I literally talked about it just one post above: https://github.com/andreicristianpetcu/google_translate_this/issues/19#issuecomment-557775532

[grahamperrin]

I mean, it's really risky …

[nl255]

Well one possible solution so that it works in Waterfox (and possibly other forks) is to modify the extension so that it no longer trips the blocklist and then simply not submit it to Mozilla to be signed at all? Surely Mozilla wouldn't go to the trouble of updating their blacklist to block extensions that don't even run on (vanilla) Firefox at all due to never having been signed in the first place.

[grahamperrin]

https://github.com/jeremiahlee/page-translator/issues/26#issuecomment-570078850

The block list does include non-signed extensions.