Talk:NPAPI

message: I don't recall Netscape 6.5 shipping. All we are aware of is a t-shirt with a prediction that turned out to be false.
I'm not sure what this should have said. But someone should have checked their sources before writing it.
192.100.124.219 12:22, 21 August 2006 (UTC)
replies: text: Good catch; I found an old Mozilla article which suggests the feature was first added in Netscape 6.1, so I'll change the article accordingly. Could still do with a more concrete source, but it's better than listing a non-existent version. - IMSoP 20:48, 28 January 2007 (UTC)
thread_title:  Netscape 6.5 

message: Writing scripting plugins with Mozilla is a dead link  —Preceding unsigned comment added by 80.177.204.14 (talk) 22:15, 30 June 2009 (UTC)
thread_title:  Dead link 

message: Its say that you can't use NPAPI prior consent of Google, i.e. while it is possible to use NPAPI, Google is "discouraging" (not allowing) to use it.. And since it is virtually impossible to contact Google (Google doesn't have a proper call center / help desk), then it virtually is disallowing to use it.
--200.83.2.4 (talk) 18:57, 24 November 2009 (UTC)
replies: text: Yes, Google discourages the use of this due to security concerns (NPAPI code must be trusted so also must be secure; NPAPI plug-ins have historically been a large source of security issues). 134.134.139.76 (talk) 01:24, 20 February 2014 (UTC)
thread_title: Google Chrome Extension

message: https://wiki.mozilla.org/NPAPI:Pepper
It says pepper is obsolete and PPAPI (pepper plugin api) or pepper2 is the new redesigned api.  —Preceding unsigned comment added by 99.240.99.150 (talk) 21:19, 4 April 2011 (UTC)
replies: text: Pepper or the PPAPI was originally implemented as a fork of NPAPI but after Mozilla backed out, Google decided to just rewrite it instead of trying to push changes back on Mozilla—so in essence it used to be a derivative work but is no longer. 134.134.139.76 (talk) 01:22, 20 February 2014 (UTC)
thread_title:  Pepper? 

message: It's probably worth noting that the GWT live debugging of generated javascript running in a browser, whilst looking at the parent java code in eclipse in a stepping debugger is all hooked together with NPAPI http://www.quora.com/How-does-GWT-live-javascript-debugging-in-Eclipse-work-and-how-could-it-be-applied-to-Clojure?__snids__=43385373  — Preceding unsigned comment added by 124.149.43.34 (talk) 12:14, 31 May 2012 (UTC)
thread_title:  GWT Debugging 

message: When I have to run a Java app that we use at work I switch from Chrome to IE 11 and I can still use the Java plugin. I believe there is direct NPAPI support in IE 11 and there has been through many earlier IE releases. The ActiveX control that was a shim is not the same thing when you're listing which browsers have NPAPI support. -- DeweyQ (talk) 17:23, 11 February 2016 (UTC)
replies: text: Internet Explorer 11 uses the ActiveX Java plugin, not the NPAPI plugin. -- Lonaowna (talk) 14:31, 13 April 2016 (UTC)
thread_title:  Internet Explorer support 

message: http://www.ghacks.net/2016/09/06/adobe-resurrects-flash-for-linux-from-the-dead/
Time to update the last part of the article. 76.254.17.57 (talk) 02:11, 8 September 2016 (UTC)
replies: text: Added. Lonaowna (talk) 11:15, 8 September 2016 (UTC)
replies: text: Thanks. 76.254.17.57 (talk) 15:33, 8 September 2016 (UTC)
thread_title:  Adobe Flash v23, Linux 

message: Hello fellow Wikipedians,
I have just modified 2 external links on NPAPI. Please take a moment to review my edit. If you have any questions, or need the bot to ignore the links, or the page altogether, please visit this simple FaQ for additional information. I made the following changes:
*Added archive https://web.archive.org/web/20170307050159/https://support.mozilla.org/t5/Problems-with-add-ons-plugins-or/Why-do-Java-Silverlight-Adobe-Acrobat-and-other-plugins-no/ta-p/31069 to https://support.mozilla.org/t5/Problems-with-add-ons-plugins-or/Why-do-Java-Silverlight-Adobe-Acrobat-and-other-plugins-no/ta-p/31069
*Added archive https://web.archive.org/web/20150906115517/https://dev.opera.com/extensions/tut_npapi.html to https://dev.opera.com/extensions/tut_npapi.html
When you have finished reviewing my changes, you may follow the instructions on the template below to fix any issues with the URLs.
Cheers.—InternetArchiveBot (Report bug) 00:02, 11 February 2018 (UTC)
thread_title:  External links modified (February 2018) 

message: It seems Apple now has their potential to drop support for Legacy Plug-ins (Except For Adobe Flash Player)
https://www.macrumors.com/2018/03/21/apple-releases-safari-technology-preview-52/  — Preceding unsigned comment added by DeveloperPudú (talk • contribs) 18:09, 17 May 2018 (UTC)
thread_title:  Inclusion of Safari Technology Preview 52's support of NPAPI? 

message: Should Uzbl still be on the list of browsers that support NPAPI, given Uzbl has been discontinued since 2016? 60.242.50.114 (talk) 12:05, 29 July 2021 (UTC)
thread_title:  Uzbl