Launchpad has imported 5 comments from the remote bug at http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1791.
If you reply to an imported comment from within Launchpad, your comment will be sent to the remote bug automatically. Read more about Launchpad's inter-bugtracker facilities at https://help.launchpad.net/InterBugTracking. ------------------------------------------------------------------------ On 2014-05-25T14:59:12+00:00 David Lenz wrote: Google Chrome 35 has dropped support for NPAPI plugins (so icedtea no longer works there). Is there a plan to make a PPAPI-compatible version of icedtea? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1308783/comments/6 ------------------------------------------------------------------------ On 2014-06-24T16:11:41+00:00 Javier Domingo wrote: I have tracked down to this bug, which seems to be the source of java applets not working on chromium. Is any update on this bug? Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1308783/comments/8 ------------------------------------------------------------------------ On 2014-06-24T17:00:20+00:00 Aazores wrote: Yes, this is indeed the cause for Java applets no longer working in Chrome/Chromium - Google has removed the plugin API which IcedTea-Web uses. We haven't yet determined if it is even possible to create a port of IcedTea-Web to PPAPI, due to the sandboxing and other restrictions Google places on extensions built with Pepper/Native Client. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1308783/comments/9 ------------------------------------------------------------------------ On 2014-06-24T21:48:13+00:00 Mattias-eliasson wrote: There are a relevant discussion about this here: http://www.firebreath.org/display/documentation/Browser+Plugins+in+a +post-NPAPI+world The short answer are that there are no sufficient replacement for NPAPI in Chrome. Chromium are open source so it could potentially be modified. Currently my brightest idea are to use DLL injection and override the entire engine component with something similar to Chrome Frame. If we simply run another browser engine, such as a modified Chromium engine with NPAPI-support, that might work. Or an engine that do not require any hacking such as Qt WebKit which supports NPAPI plugins out of the box. Another option would be to make a completely Chrome-compatible browser out of Chromium, which are what the Qt WebEngine are all about. Such a browser could be entirely FOSS and shipped with Linux distributions. A mayor problem would be the Flash plugin which may require that Chrome are also installed. As a system admin I would like to avoid installing Chrome in such a scenario, or at least hide it well. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1308783/comments/10 ------------------------------------------------------------------------ On 2014-06-26T07:54:33+00:00 helpcrypto wrote: Altough a bug report is not the best place to chat, I'll give you my 2 cents: - Assume you arent going to use Chrome for a while. Firefox, Safari and IE will work. - If possible, use JNLP. AFAIK it will continue working. - If you, like me, are using applets for electronic signature, probably the best option is to keep praying for Webcrypto+FIDO Regards. Reply at: https://bugs.launchpad.net/ubuntu/+source/chromium- browser/+bug/1308783/comments/11 ** Changed in: icedtea Status: Unknown => Confirmed ** Changed in: icedtea Importance: Unknown => High -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1308783 Title: chromium-browser: No Java Pepper Plugin available To manage notifications about this bug go to: https://bugs.launchpad.net/chromium-browser/+bug/1308783/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
