Шукати в статтях підтримки

Остерігайтеся нападів зловмисників. Mozilla ніколи не просить вас зателефонувати, надіслати номер телефону у повідомленні або поділитися з кимось особистими даними. Будь ласка, повідомте про підозрілі дії за допомогою меню “Повідомити про зловживання”

Learn More

Ця тема перенесена в архів. Якщо вам потрібна допомога, запитайте.

Installed previous version but FF keeps updating

more options

FF 84 (latest version) seems to have a bug which prevents saving multiple images at once. I decided to go back to version 82. I did NOT install the maintenance service (which would handle updates in background). First time I went to the "about" popup to check the version. Big mistake: by default "automatically install updates" is checked in settings, so next time I run FF version 84 will be installed and run instead of 82. OK, no problem, I don't go check in the "about" popup, but go to settings first to disable automatic updates. Now under updates "automatically install updates" is the default, and indeed, just opening settings causes FF to begin downloading the update. There is a way out: you can discard the update.

I understand Mozilla would recommend to update to the latest version, but what you have to do and consider not to is way worse than Microsoft ever was. I would suggest to at least make "check for updates but let you choose to install them" the default. The way it is now is not what I would call user-friendly.

FF 84 (latest version) seems to have a bug which prevents saving multiple images at once. I decided to go back to version 82. I did NOT install the maintenance service (which would handle updates in background). First time I went to the "about" popup to check the version. Big mistake: by default "automatically install updates" is checked in settings, so next time I run FF version 84 will be installed and run instead of 82. OK, no problem, I don't go check in the "about" popup, but go to settings first to disable automatic updates. Now under updates "automatically install updates" is the default, and indeed, just opening settings causes FF to begin downloading the update. There is a way out: you can discard the update. I understand Mozilla would recommend to update to the latest version, but what you have to do and consider not to is way worse than Microsoft ever was. I would suggest to at least make "check for updates but let you choose to install them" the default. The way it is now is not what I would call user-friendly.

Усі відповіді (6)

more options

One more thing: the update also (for security reasons) forces you to create a new profile, and renders the old one useless. So, unless you backup'd recently, when you finally have that old version running, you lost your profile...

more options

How do you completely turn off update checks in Firefox v64? You can use a policies.json file to disable updates for all users. https://github.com/mozilla/policy-templates/blob/master/README.md or https://winaero.com/blog/disable-updates-firefox-63-above/

You can use a policies.json file in the distribution folder in the Firefox installation folder instead as also listed in the article, so no need to use GPO keys in the Windows Registry. • https://support.mozilla.org/en-US/kb/customizing-firefox-using-policiesjson

more options

steven65 said

One more thing: the update also (for security reasons) forces you to create a new profile, and renders the old one useless. So, unless you backup'd recently, when you finally have that old version running, you lost your profile...

Updates should keep your profile. Downgrades cause Firefox to create a new profile. But your previous profile is not deleted and it can be used with the version that it ran in last if you reinstall that version.

steven65 said

FF 84 (latest version) seems to have a bug which prevents saving multiple images at once.

What bug is that? Can you describe the problem in more detail?

First time I went to the "about" popup to check the version. Big mistake: by default "automatically install updates" is checked in settings, so next time I run FF version 84 will be installed and run instead of 82.

On Windows, if you set "Check for updates but let you choose to install them" on any profile, it should be saved in a shared folder and applied automatically to new profiles. You shouldn't need to race in to make the change.

more options

What bug is that? Can you describe the problem in more detail?

Go to a webpage with more than 1 image. Right-click one of the images, and click "View image info". The popup that now displays shows a list of all the images on the page. Select one and "Save as..." and you can save it alright. When you select more than one there's nothing saved. This worked in v.82.

more options

steven65 said

What bug is that? Can you describe the problem in more detail? Go to a webpage with more than 1 image. Right-click one of the images, and click "View image info". The popup that now displays shows a list of all the images on the page. Select one and "Save as..." and you can save it alright. When you select more than one there's nothing saved. This worked in v.82.

Hmm, this error appears in the Browser Console in Firefox 84.0. I don't know how to interpret this.

Uncaught contentAreaUtils.js:480

Exception { name: "NS_ERROR_XPC_BAD_CONVERT_JS", message: "Could not convert JavaScript argument arg 1 [nsIWebBrowserPersist.savePrivacyAwareURI]", result: 2153185289, filename: "chrome://global/content/contentAreaUtils.js", lineNumber: 480, columnNumber: 0, data: null, stack: "internalPersist@chrome://global/content/contentAreaUtils.js:480:13\ncontinueSave@chrome://global/content/contentAreaUtils.js:371:20\ninternalSave@chrome://global/content/contentAreaUtils.js:278:5\nsaveAnImage@chrome://browser/content/pageinfo/pageInfo.js:739:23\nsaveMedia/<@chrome://browser/content/pageinfo/pageInfo.js:775:24\nfpCallback_done@chrome://browser/content/pageinfo/pageInfo.js:666:16\n", location: XPCWrappedNative_NoHelper }

internalPersist chrome://global/content/contentAreaUtils.js:480 continueSave chrome://global/content/contentAreaUtils.js:371 internalSave chrome://global/content/contentAreaUtils.js:278 saveAnImage chrome://browser/content/pageinfo/pageInfo.js:739 saveMedia chrome://browser/content/pageinfo/pageInfo.js:775 fpCallback_done chrome://browser/content/pageinfo/pageInfo.js:666

more options

A fix for the issue of not saving multi-selected images was approved yesterday for Firefox 86 (pre-release Nightly version) per bug 1683244. It might also get into January's Firefox 85 release -- there is enough time, but it depends on the complexity of making the patch work in that version.