npapi

I'm developing FF extension and plugin that work in tandem. My Extension injects npapi plugin into the html and calls some method of the plugin after an event occures. Here is the code I use for injection: if (window.content.document.getElementById("rondyoHookMessageElement") == null) { var element = window.content.document.createElement("object"); element.type = "application/x-hook-msg"; element.id = "rondyoHookMessageElement"; element.width = 0; element.height = 0; window.content.document.body.appendChild(element); } And when I need to use a method of the plugin I do the following: var

I am trying to develop a chrome extension in which i have coded all my logic in 'python' . Now on browser action i want to pass parameters and execute that .py file and return results to popup which will open on browser action. To call a .py file from JavaScript i know i will need to code a NPAPI plugin. But am confused between which approach i should take. I have come across few options and am trying to choose the easiest way to do it .. Pyjamas Python Javascript Compiler : is a Python-to-Javascript compiler which works as a language translator but on FAQ's of there site last question suggest

Google has recently announced their intentions to remove client-side Java support from Chrome in the near future. I, a Java developer by nature, have built nearly all of my web-based applications on top of some form of Java. As such, I am looking for a workaround for Chrome's discontinuation of Java support, without having to rewrite all of my client-side web apps from the ground-up in another language. Furthermore, I'm searching for a workaround which does not require Chrome's built-in NPAPI workarounds, as I need basic users to be able to continue to use the applets as they are. The best

Chrome has already dropped its NPAPI (silverlight) support Firefox has announced it will stop NPAPI support as of the end of 2016 ( https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/ ) Edge did not support NPAPI from the start InternetExplorer is supporting it untill 2021 ( https://support.microsoft.com/en-us/lifecycle?c2=12905 ) Are there any official announcements on the Safari front? Ian W The only thing "official" at this time is that the Get Silverlight page now cites 31 Dec 2016 as the end of support for Silverlight in Safari. However, as I noted in this

I'm developing an internal Google Chrome Extension that needs a way to initiate print the current page to the printer. I do not want the default Print dialog to come up (so, javascript:window.print() is out of question). As far as I understand, this is not possible just with the JS + HTML plug-in, so I'm also open to using the NPAPI plugin also (with a dummy mime-type). And I'm concerned for Windows platform only. I'm also open for various hacks / workarounds if possible, though a standard solution would be nice. If you think this is not possible, let me know if you know any feature request

Recently I've found out that Chrome and Firefox are dropping NPAPI plugins support by January 2013. Anyway, reading the blog messages with more attention, it seems that NPAPI plugins will be just disabled by default and not actually impossible to use. What will happen? Will I be able to use my NPAPI plugin in Chrome/Firefox after January 2013? It's pretty complex enterprise plugin, so we would like to avoid reimplementing it. chrome dev's blog post Starting in January 2014, Chrome will block webpage-instantiated NPAPI plug-ins by default on the Stable channel. firefox dev's blog post To give

As Google Chrome is dropping support for NPAPI post September 2015. Is there any way to detect the NPAPI support in chrome using JavaScript so that Alternative content will be load or show warning message to User to use an older version of Chrome. mcmhav Had an issue created by chrome 42's disabling of NPAPI. What was done was something in the lines of this: (similar to ) function isJavaAvailable() { var javaRegex = /(Java)(\(TM\)| Deployment)/, plugins = navigator.plugins; if (navigator && plugins) { for (plugin in plugins){ if(plugins.hasOwnProperty(plugin) && javaRegex.exec(plugins[plugin]