When does Opera stop supporting NPAPI Plugins

  • As you know Opera has been counting down to step away NPAPI Plugins
    I should to have NPAPI Plugins, Adobe Reader, to work with my routine jobs
    SO SADDD

  • There are PPAPI PDF plugins for Opera. Opera getting ride of NPAPI wont make it so you can't read PDFs.

  • As far as when ... whenever Chromium does. Opera will neither remove the code themselves nor add it back once it has been dropped from Chromium, so once that version of Chromium lands in Opera is when NPAPI plugins stop working.

  • Chrome 45 dropped NPAPI a few days ago (hence my now using Opera...which is noticeably faster and smoother).

    Can I get a definitive response on whether NPAPI (specifically Java) support will continue or be dropped? I'd rather not be in the same situation again.

  • ...
    Can I get a definitive response on whether NPAPI (specifically Java) support will continue or be dropped? ...

    If Opera doesn't control the chromium engine which Opera employs in its browser, then it doesn't control whether the dropping of NPAPI plug-ins will be incorporated into chromium. If the dropping of NPAPI does get incorporated into chromium, then it will ripple through Opera's updating process to appear in an Opera version soon thereafter, unless Opera were to insert its own freeze on further chromium updating within its browser - something that's extremely unlikely since all manner of other changes will keep rolling down the chromium engine pipeline, including security updates. The definitive answer you seek depends on what the chromium designers decide to do, not what the Opera developers decide.

  • You missed the other option - as Chromium already did from Safari, in theory Opera could "fork" the code (make their own branch) ... but then they'd be left backporting all the bug fixes made to Chromium to their code. Not practical for a small company, really.

  • Yeah... I chose to omit that because Opera, in walking away from their own Presto rendering engine, is hardly likely to get half-way back into the rendering engine business by forking the chromium engine and having to maintain that.

  • Perhaps. I don't know how modular Chromium is or how labour-intensive it is to customise. Since Opera behaves differently than Chrome, it has to be more than just a skinned Chromium.

    Chrome is Chrome 45 but has no NPAPI support.
    Opera 32 is Chrome 45 but supports NPAPI still.
    Opera 33 & 34 are Chrome 46 but still have NPAPI support (it has to be manually enabled through flags).
    All are WebKit 537.36.

    I really, really won't want to have to use Firefox. Despite its benchmarking higher (no idea why but it's not the only benchmark to not reflect the real-world), its rendering is painfull, slow, and jerky.

  • NPAPI plugins in browsers are almost dead already.

    @rolox2, you know Firefox has promised to drop NPAPI plugins by the end of 2016:

    https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox

Log in to reply
 

Looks like your connection to Opera forums was lost, please wait while we try to reconnect.