On 9/23/2013 4:29 PM, Hubert Figuière wrote:
Hi all,
Today Google said they'd drop NPAPI for good.
We also intend to someday drop NPAPI for good. I don't think that "by
the end of 2014" is a realistic timeline for either Chrome or us, given
the number of users who still rely on Java and other plugins. But we're
certainly looking into the places where people currently "need" plugins
and are trying to create or implement web APIs to address those needs.
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.
Too late for what? What are you concerned about? We are not constrained
by Chrome's decision to drop NPAPI. Right now Flash is the only
significant plugin that is using pepper, and it also has a supported
NPAPI version. We're also working on a pure-JS replacement (Shumway)
which is going quite well.
The costs of Pepper are huge: it is not a well-specified API; we'd be
reverse-engineering large bits of chromium code in order to support it,
and it's clear that we want to focus effort on the web not Pepper. Given
that Pepper presents little benefit to users, I don't think it makes any
sense to focus on it relative to other things such as graphics
performance, web API improvements, and asm.js which can serve the sam
general niche as plugins, but will improve the open web at the same time.
--BDS
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
