Google today provided an update on its plan to remove Netscape Plugin Application Programming Interface (NPAPI) from Chrome, which the company says will improve the browser's security, speed, and ...

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 ...

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 ...

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 ...

Reliant on plug-ins like Silverlight, Unity, and Java? Make plans to move on or change browsers, because most plug-ins will be banned from Chrome in the next year. Stephen Shankland worked at CNET ...

Changing Web usage is hard. Google has granted a few extra months of leeway to those who rely on a handful of popular plug-ins, such as Silverlight, to extend what their browser can do. Stephen ...

The clock is ticking for plug-ins in Chrome based on the NPAPI standard; here's what you need you know about how it will affect enterprise use Last year, Google announced it was embarking on a ...

Google on Monday gave traditional Google plug-ins a stay of execution and instead outlined a three-step plan that will finalize their demise in 10 months. The delay was the latest move in a year-long ...

In June last year the Google Chrome team announced that they would be ending support for NPAPI based plugins by September 2014. NPAPI is an ageing technology used by, most notably, Java, Silverlight ...

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 ...