[Bug 1791] PPAPI (pepper) version

[bugzilla-daemon at icedtea.classpath.org]

http://icedtea.classpath.org/bugzilla/show_bug.cgi?id=1791

Mattias Eliasson <mattias.eliasson at medsa.se> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |mattias.eliasson at medsa.se

--- Comment #3 from Mattias Eliasson <mattias.eliasson at medsa.se> ---
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.

-- 
You are receiving this mail because:
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.openjdk.java.net/pipermail/distro-pkg-dev/attachments/20140624/8eea607c/attachment.html>