Rechercher dans l’assistance

Évitez les escroqueries à l’assistance. Nous ne vous demanderons jamais d’appeler ou d’envoyer un SMS à un numéro de téléphone ou de partager des informations personnelles. Veuillez signaler toute activité suspecte en utilisant l’option « Signaler un abus ».

En savoir plus

Should the Java Plug-in 2 for NPAPI 1.6.0.31 be disabled?

  • 1 réponse
  • 3 ont ce problème
  • 3 vues
  • Dernière réponse par philipp

more options

I was updating my Google Blogger sites, and got a Firefox error message that I believe said that the Java Plug-in 2 for NAPAPI 1.6.0.31 should be disabled, and I should restart Firefox. I decided to sign out of my Blogger account before disabling the plugin, but when I did so, the Firefox error message was no longer there (so that's why I'm not positive it was that plugin). I went into the Plugin Check page and and see that the plugin is "up to date." Should I disable it anyway?

I was updating my Google Blogger sites, and got a Firefox error message that I believe said that the Java Plug-in 2 for NAPAPI 1.6.0.31 should be disabled, and I should restart Firefox. I decided to sign out of my Blogger account before disabling the plugin, but when I did so, the Firefox error message was no longer there (so that's why I'm not positive it was that plugin). I went into the Plugin Check page and and see that the plugin is "up to date." Should I disable it anyway?

Solution choisie

hello, java versions including 1.6.0_31 & upwards should not be blocked by firefox, i don't know why you got the notification in the first place (maybe the block was implemented when there was still an out-of-date version of the plugin on your pc & the plugin update happened immediately afterwards).

https://addons.mozilla.org/firefox/bl.../p85

Lire cette réponse dans son contexte 👍 1

Toutes les réponses (1)

more options

Solution choisie

hello, java versions including 1.6.0_31 & upwards should not be blocked by firefox, i don't know why you got the notification in the first place (maybe the block was implemented when there was still an out-of-date version of the plugin on your pc & the plugin update happened immediately afterwards).

https://addons.mozilla.org/firefox/bl.../p85

Modifié le par philipp