5 段階中 4.5 の評価
5 段階中 4.6 の評価
- Firefox ユーザー 15151213 によるレビュー (5ヶ月前)5 段階中 3 の評価Installation aborted because the add-on appears to be corrupt. -- I gave this add-on three stars because I had to rate it to write some sort of feed back. But when I try to install add-on the message I get is,"Installation aborted because the add-on appears to be corrupt."
開発者の返信投稿日時: 3ヶ月前If you can't install the add-on it's a problem of addons.mozilla.org and has nothing to do with the add-on itself. I don't have any control about the installation process of add-ons on this website.
- Join2 によるレビュー (10ヶ月前)5 段階中 5 の評価Small remark. New FF version installation distribution(policy) gone. First time FF64 and now 65, have to start configure again. Backup EPG(json) before FF version update.
- Anton によるレビュー (1年前)5 段階中 5 の評価"DisableTelemetry": true
I am particularly interested in disabling telemetry. Is telemetry really will be COMPLETELY disabled or is this option equivalent to unchecking the checkboxes in browser settings page? Disable telemetry, health reports, experiments, activity streams and other shit - that is what I want to do.I don't understand your comment because telemetry is telemetry. Health Report is no longer a thing, activity stream is only another word for the default new tab page and has nothing to do with telemetry at all and I don't know what you mean with "shit".
By the way: In my opinion it's a bad idea to disable telemetry because telemetry is not for Mozilla, it's for you. If you disable telemetry then, please, don't complain if Mozilla removes your favourite feature from Firefox because the data tells Mozilla that nobody needs this particular feature. ;)
- Firefox ユーザー 14375314 によるレビュー (1年前)5 段階中 5 の評価It doesn't work. I'm using the portable ff 63 version - could that be the reason? If I can't find how to stop this automatic update (forced down our throat) , I'll revert back to v62. My thanks to the developer nonetheless.The Enterprise Policy Generator works, that's sure. The reason is simple: The Enterprise Policy Generator only generates the JSON content, it's not possible that something goes wrong in this step. ;-) If a policy does not work then either the content of the policy is wrong or there is a bug in Firefox. Or you didn't put the file into the correct directory.
If you open a GitHub issue with steps to reproduce your problem then I'll have a look.
By the way: You can use the Enterprise Policy Generator to disable Firefox updates, but really, you shouldn't do that. There is nothing more important than to update your browser for security reasons.