NPP_DrawImage NPAPI proposal.

Antoine Labour piman at
Thu Apr 8 15:54:00 PDT 2010

On Thu, Apr 8, 2010 at 2:12 PM, Robert O'Callahan <robert at>wrote:

> On Fri, Apr 9, 2010 at 8:23 AM, Antoine Labour <piman at> wrote:
>> Another point: significant work has already been invested into the
>> platform independent NPAPI to redefine 2D drawing into something that works
>> better for untrusted and OOP plugins, and that work is supported by 2
>> browser vendors
> Hmm, who other than Chrome?

According to both
is working on it too...

>  and 1 major plugin vendor (see
>> ),
>> so I would suggest bringing your thoughts into the design there, rather than
>> bringing a 3rd drawing model to the table.
> There is no consensus that Pepper is the future of NPAPI, and it's such a
> huge API that implementing Pepper well in a browser is a very large project.
> I don't think we should allow the possibility of Pepper in the future to
> block incremental improvements to the rest of NPAPI.

Well, I'm not sure if browser vendors in general are interested in
supporting a wide variety of redundant efforts...
Note that most parts of Pepper can be incrementally bolted on existing NPAPI
implementations, so you don't have to fully implement Pepper to implement
the 2D drawing part.


> Rob
> --
> "He was pierced for our transgressions, he was crushed for our iniquities;
> the punishment that brought us peace was upon him, and by his wounds we are
> healed. We all, like sheep, have gone astray, each of us has turned to his
> own way; and the LORD has laid on him the iniquity of us all." [Isaiah
> 53:5-6]
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the plugin-futures mailing list