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!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Mear ynfo

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

NPAPI support in Firefox

  • 1 antwurd
  • 5 hawwe dit probleem
  • 5 werjeftes
  • Lêste antwurd fan the-edmeister

user331284248850114401759811723737644008406
user331284248850114401759811723737644008406
more options

I'm going to put effort into NPAPI plugin developement. My question: Will Firefox continue to support NPAPI, or will Firefox drop NPAPI support in future releases?

If it will be dropped, will there be any alternatives for executing native code?

br Gerhard

I'm going to put effort into NPAPI plugin developement. My question: Will Firefox continue to support NPAPI, or will Firefox drop NPAPI support in future releases? If it will be dropped, will there be any alternatives for executing native code? br Gerhard

Alle antwurden (1)

the-edmeister
the-edmeister
  • Moderator
more options

Two sides to the coin flip.

This page - https://wiki.mozilla.org/NPAPI - is dated 4 February 2014 and mentions NPAPI current specs and specs under consideration in the future.

This - http://www.firebreath.org/display/documentation/Browser+Plugins+in+a+post-NPAPI+world - isn't from Mozilla, but there's enough in that article that should have plugin developers starting to question the wisdom of investing a lot of time with NPAPI plugin development. How much of that applies to the future of NPAPI and Mozilla is questionable, since that 'group' seems to focus on Chrome more than Mozilla.