This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Avatar for Username

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

Thread ini telah diarkib. Sila tanya soalan baru jika anda perlu bantuan.

NPAPI support in Firefox

  • 1 balasan
  • 5 ada masalah ini
  • 3 paparan
  • Balasan terakhir oleh the-edmeister

Nertsch
Nertsch
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

All Replies (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.