Pepper is not an API, its basically a huge set of Chromium guts exposed you can link against. The only documentation is the source, and that source keeps constantly changing. I don't think its viable for anyone to implement Pepper without also pulling in most or all of Chromium. Pepper is Chrome, and Chrome is Pepper. This is the reason that we won't-fixed bug 729481, and nothing has changed since then. I don't think we should spend energy on getting onto Google's Pepper treadmill. We should instead continue to accelerate the decline of plugins by offering powerful new HTML5 capabilities that obsolete plugins.
Andreas On Sep 23, 2013, at 1:29 PM, Hubert Figuière <h...@mozilla.com> wrote: > Hi all, > > Today Google said they'd drop NPAPI for good. > > http://news.cnet.com/8301-1023_3-57604242-93/google-begins-barring-browser-plug-ins-from-chrome/ > > Bug 729481 was WONTFIXED a while ago. tl;dr : implement Pepper plugin API > > I think it might be worth the revisit that decision before it is too late. > > > Hub > > PS: I truly believe that we should drop plugin support all together, but > that's not what I'm discussing here. > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
