Avatar for Username

Eheka Pytyvõha

Emboyke pytyvõha apovai. Ndorojeruremo’ãi ehenói térã eñe’ẽmondóvo pumbyrýpe ha emoherakuãvo marandu nemba’etéva. Emombe’u tembiapo imarãkuaáva ko “Marandu iñañáva” rupive.

Kuaave

Ko téma oñeñongatúma. Ejapo porandu pyahu eikotevẽramo pytyvõ.

NPAPI support in Firefox

  • 1 Mbohovái
  • 5 oguereko ko apañuãi
  • 3 Hecha
  • Mbohovái ipaháva 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

Opaite Mbohovái (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.