Hilfe durchsuchen

Vorsicht vor Support-Betrug: Wir fordern Sie niemals auf, eine Telefonnummer anzurufen, eine SMS an eine Telefonnummer zu senden oder persönliche Daten preiszugeben. Bitte melden Sie verdächtige Aktivitäten über die Funktion „Missbrauch melden“.

Learn More

Feature Request: Check preservation of plug-ins before update; select suitable update; ask user for update permission!

  • 3 Antworten
  • 1 hat dieses Problem
  • 23 Aufrufe
  • Letzte Antwort von James

more options

Mozillas regularily forces updates in some applications, regardless if plug-ins will run in the updated version. This mechanism is obviously not meant to be blocked by the user in any way.

For me - and I think, I am not alone - Firefox is only the browser of choice thanks to certain plug-ins. Speed, security, design, usability - Firefox and Thunderbird are worthless, if my essential plug-ins are absent.

I design my systems to be near maintenance free, so the last thing I need is a browser update that smashes everything and makes my users mad. Workarounds for the annoying screwed up update policy is costing me ever more time.

Please, can you: - build in a routine to check the availbility for selected plug-ins BEFORE updating - advanced: if there are multiple target versions, automatically select the newest one that

 supports the whole set of selected plug-ins

- ask the user if he wants an update

and first of all:

- refrain reliably from updating when the USER or ADMINISTRATOR does not want it; ask him so.

 --> Do not update just because someone clicked on 'About'

PLEASE.

Mozillas regularily forces updates in some applications, regardless if plug-ins will run in the updated version. This mechanism is obviously not meant to be blocked by the user in any way. For me - and I think, I am not alone - Firefox is only the browser of choice thanks to certain plug-ins. Speed, security, design, usability - Firefox and Thunderbird are worthless, if my essential plug-ins are absent. I design my systems to be near maintenance free, so the last thing I need is a browser update that smashes everything and makes my users mad. Workarounds for the annoying screwed up update policy is costing me ever more time. Please, can you: - build in a routine to check the availbility for selected plug-ins BEFORE updating - advanced: if there are multiple target versions, automatically select the newest one that supports the whole set of selected plug-ins - ask the user if he wants an update and first of all: - refrain reliably from updating when the USER or ADMINISTRATOR does not want it; ask him so. --> Do not update just because someone clicked on 'About' PLEASE.

Alle Antworten (3)

more options

Hi,

The people who answer questions here, for the most part, are other Firefox users volunteering their time (like me), not Mozilla employees or Firefox developers.

If you want to leave feedback for Firefox developers, you can go to the Firefox Help menu and select Submit Feedback... or use this link. Your feedback gets collected by a team of people who read it and gather data about the most common issues.


I have refused to update for similar reasons.

more options

1. You posted here with an old version of Firefox 52 which has long since been unsupported by Mozilla.

2. Plugins are no longer supported (beyond the Flash plugin) by almost all current web browsers.

3. As far as Mozilla forcing updates - program security updates for both Firefox and Thunderbird can quite easily be disabled in a few ways. Just search this forum - https://support.mozilla.org/en-US/search/advanced - to learn how.

more options

Why do Java, Silverlight, Adobe Acrobat and other plugins no longer work? https://support.mozilla.org/en-US/kb/npapi-plugins

The only NPAPI Plugin allowed to run in Firefox since the Fx 52.0 Release has been Flash Player from Adobe. The Fx 52 ESR for Enterprise users was an exception at time.

Chromium, Chrome, and Opera dropped NPAPI Plugins support back in Sept 2015.

Oracle has been depreciating their Java Plugin as it is not in Java 9. However Java web start may be an option.

Adobe is in process of ending their Flash Player Plugin by end of 2020. https://blog.mozilla.org/futurereleases/2017/07/25/firefox-roadmap-flash-end-life/

Geändert am von James