With the release of Chrome 42 this week, Google fixed more than 40 vulnerabilities. But the most significant security change in the new browser is Google’s decision to disable the NPAPI, essentially ...

A monthly overview of things you need to know as an architect or aspiring architect. Unlock the full InfoQ experience by logging in! Stay updated with your favorite authors and topics, engage with ...

A recently released update to Chrome has brought a plan to the forefront that has been brewing behind the scenes since 2013: the deprecation of NPAPI (Netscape Plugin Application Programming Interface ...

The add-on facilitates connections to TWAIN-based scanners in Chrome versions requiring HTML5-based plugins. With 10 years of experience in TWAIN and imaging SDKs ...

Chrome 42, released to the stable channel today, will take a big step toward pushing old browser plugins, including Java and Silverlight, off the Web. Those plugins use a 1990s-era API called NPAPI ...

Plug-ins based on the NPAPI architecture will be blocked by default in Chrome starting early next year as Google moves toward completely removing support for them in the browser. “NPAPI’s 90s-era ...

Starting in January 2015, Google’s Chrome browser will block all old-school Netscape Plug-In API (NPAPI) plugins. This doesn’t come as a huge surprise, given that Google started its efforts to remove ...

It’s been a long time coming, Google has come forward and said that it will remove Netscape Plugin Application Programming Interface (NPAPI) from Chrome. The Mountain View giant also said that this ...