We're calling on all EU-based Mozillians with iOS or iPadOS devices to help us monitor Apple’s new browser choice screens. Join the effort to hold Big Tech to account!

Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

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

  • 1 tontu
  • 3 am na jafe-jafe bii
  • 1 view
  • i mujjee tontu mooy 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?

Saafara biñ tànn

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

Jàng tontu lii ci fi mu bokk 👍 1

All Replies (1)

more options

Saafara yiñ Tànn

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

philipp moo ko soppali ci