![]() This is true, but Page Translator’s methods do not subvert Firefox’s cookie and tracker blocking. Mozilla could argue that loading these language translation libraries onto a page enables Google or Microsoft to track users. There is no deception on my part to the user or to Mozilla about the behavior of the add-on. The code for loading these libraries is not obfuscated and is public. Page Translator adds these libraries as if they had been included on the webpage by the webpage author using the methods prescribed by Google and Microsoft to website owners. Page Translator, as explicitly stated to users, load Google Translator or Microsoft Translate. It cannot do that when an extension loads external, obfuscated code. By distributing a browser extension, Mozilla is effectively vouching for its credibility. I understand and agree with a general policy of browser extensions needing to be self-contained. Update : Mozilla responded to my request for more information and confirmed the policy change and the block being permanent. I have emailed the AMO team for more information. The add-ons manager in Firefox directed me to a page explaining the removal and this Bugzilla ticket. Mozilla remotely disabled Page Translator for the thousands of people who use it, once again, without warning and without contacting me, the developer. Only, Page Translator had been removed from my browser, without my consent. I rely on in-line language translation in the browser to supplement my nascent Swedish literacy. ![]() I am an American living in Sweden and many government websites are only available in Swedish. This morning, I opened up Firefox and wanted to translate a page in Swedish. Screenshot of Mozilla Add-ons policy when Page Translator was last released, via the Internet Archive. I made it available for installation from its Github repository. They don’t have a way to convert an add-on from a Mozilla-hosted add-on to a self-distributed add-on, so I created a new add-on in order to sign the code for distribution. Mozilla said I could self-distribute it as a side-loaded add-on. Until some point recently, that rule only applied to add-ons distributed through. Mozilla tightened its add-on rules to not permit extensions from loading external JavaScript. ![]() Then, Mozilla killed it without discussion. Thousands of people used it and loved it. This brought in-line language translation to Firefox users. I created a Firefox extension ( Page Translator) that inserts either the Google Translate or Microsoft Translator library into a webpage, as if the website owner had included it. This allows website owners to offer their websites in another language for visitors who use browsers like Safari and Firefox that do not have in-line language translation built-in. They provide a JavaScript library website owners can add to their websites to allow in-line language translation. Google Chrome and Microsoft Edge are the only browsers to offer in-browser language translation.īoth Google and Microsoft operate language translation services. In-line language translation in the browser is a necessary feature for millions of people who do not speak the dominant languages online. Summary: Firefox has made the Web less accessible to people who need to access information in another language, taken an absolutist position, and removed freedom of users to extend their browser.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |