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

ログインして、InfoQのすべての体験をアンロックしましょう！お気に入りの著者やトピックの最新情報を入手し、コンテンツと交流し、限定リソースをダウンロードできます。 何千人もの開発者が、InfoQのミニブック「Practical Guide to Building an API Back End 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 ...

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

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

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

Binary browser plugins using the 1990s-era NPAPI (“Netscape Plugin API”, the very name betraying its age) will soon be almost completely squeezed off the Web. Microsoft dropped NPAPI support in ...

The so-called older plugins in Google's Chrome browser will get a delay in execution, from end-2014 to sometime in September 2015. Software engineer Justin Schuh said they plan to phase out the old ...