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

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

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

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

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

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