Please read the mailing list thread I linked. It isn&#x27;t a long thread.<p>The problem is not just that PPAPI is unspecified, although that is a problem. The problem is that the consensus is&#x2F;was that PPAPI is the wrong approach entirely, because we already have the Web APIs. Inventing parallel APIs instead of providing a way for native code to call Web APIs just adds a lot of complexity to the platform for no reason.<p>&gt; It&#x27;s not as if you even need to have a formal spec for the plugin API! The previous standard, &quot;NPAPI&quot;, is the Netscape Plugin API, which was informally specified for Netscape, and then adopted by other browser vendors.<p>Nobody&#x27;s happy with NPAPI. That&#x27;s why it&#x27;s being dropped. &quot;Just as good as NPAPI&quot; is not the bar we want to meet in 2015.