Re: Howto get an NPAPI plugin added to the whitelist ?

Forgot to ask:
is there any other non-legacy native API recommended by Mozilla? 
Chrome has NaCL and PPAPI.


Am Mittwoch, 20. November 2013 14:38:43 UTC+1 schrieb [email protected]:
> Good to hear that NPAPI plugins will remain possible with Firefox.
> 
> 
> 
> It is the only browser independent native plugin API, so Google's
> 
> strategy is moving to a closed environment.
> 
> 
> 
> Is it possible to add NPAPI plugins to official catalogs or the marketplace?
> 
> 
> 
> Does it need to be wrapped as XPI then, or is XPI legacy as well for NPAPI?
> 
> 
> 
> - OL
> 
> 
> 
> Am Freitag, 15. November 2013 14:23:18 UTC+1 schrieb Benjamin Smedberg:
> 
> > On 11/15/2013 2:19 AM, ron wrote:
> 
> > 
> 
> > > source: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html
> 
> > 
> 
> > >
> 
> > 
> 
> > > Question: How can I get the NPAPI pluging added to the whitelist ?
> 
> > 
> 
> > Are you asking about the Chrome whitelist or Firefox? If you're asking 
> 
> > 
> 
> > about Chrome, you would need to talk to the Chrome engineering team 
> 
> > 
> 
> > directly, as they probably don't monitor this list.
> 
> > 
> 
> > 
> 
> > 
> 
> > Mozilla's position on plugins is represented here: 
> 
> > 
> 
> > https://blog.mozilla.org/futurereleases/2013/09/24/plugin-activation-in-firefox/ 
> 
> > 
> 
> > Plugins are considered a legacy technology, but we don't have any plans 
> 
> > 
> 
> > to remove NPAPI from our desktop products in the near future.
> 
> > 
> 
> > 
> 
> > 
> 
> > Chrome's plan to remove NPAPI seems like unrealistic posturing to me.
> 
> > 
> 
> > 
> 
> > 
> 
> > At the present time, we are whitelisting Flash but no other plugins in 
> 
> > 
> 
> > Firefox. We are discussing the option of whitelisting some other plugins 
> 
> > 
> 
> > for a while (maybe a year) while they work on transitioning to web 
> 
> > 
> 
> > technologies. Currently we don't have a decision on policy on this issue.
> 
> > 
> 
> > 
> 
> > 
> 
> > --BDS