Date: Sun, 5 May 2019 11:11:36 +0200 From: Erwan David <erwan@rail.eu.org> To: freebsd-questions@freebsd.org Subject: Re: firefox 66.0.3 disables noscript Message-ID: <a69fbc19-4b7e-abec-785c-0383637aa145@rail.eu.org> In-Reply-To: <20190505083949.3d14b628.freebsd@edvax.de> References: <9ec48bde-8880-555a-58bb-a4bb74793c96@dreamchaser.org> <201905050718.39277.dr.klepp@gmx.at> <20190505083949.3d14b628.freebsd@edvax.de>
next in thread | previous in thread | raw e-mail | index | archive | help
Le 05/05/2019 à 08:39, Polytropon a écrit : > On Sun, 5 May 2019 07:18:39 +0200, Dr. Nikolaus Klepp wrote: >> Not only noscript, but all extensions. > Correct! > > > >> But you can get them working again: >> >> about:config, then set: >> xpinstall.signatures.required=false > Similar problem here, noticed selected language was no longer > working. There is an additional setting that might help with > the language packs: > > about:config > intl.locale.requested = de > extensions.langpacks.signatures.required = false > > However, this should be just a temporary fix. FF suggests you > delete and re-install the signed (!) versions of your extensions > and language packs. > > https://blog.mozfr.org/post/2019/05/Mise-a-jour-%3A-les-modules-complementaires-de-Firefox (in french) says that it could lead to dataloss
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?a69fbc19-4b7e-abec-785c-0383637aa145>