Linked by Thom Holwerda on Mon 24th Nov 2014 19:43 UTC

Currently Chrome supports NPAPI plugins, but they are blocked by default unless the user chooses to allow them for specific sites (via the page action UI). A small number of the most popular plugins are whitelisted and allowed by default. In January 2015 we will remove the whitelist, meaning all plugins will be blocked by default.

In April 2015 NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store. Although plugin vendors are working hard to move to alternate technologies, a small number of users still rely on plugins that haven’t completed the transition yet. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI while they wait for mission-critical plugins to make the transition.

Definitely a big chance some Chrome users will have to account for.

Thread beginning with comment 600208
To read all comments associated with this story, please click here.
Java Plugin on Linux
by jasutton on Mon 24th Nov 2014 23:05 UTC
Member since:

Meanwhile, Linux users still cannot use Chrome on pages that utilize the Java plugin, as it is still using NPAPI, and (as far as I know) any of the "override" flags that allow you to re-enable NPAPI don't work on Linux.

Thanks Google.

Reply Score: 5

RE: Java Plugin on Linux
by Jedd on Tue 25th Nov 2014 07:36 in reply to "Java Plugin on Linux"
Jedd Member since:

Right. I concur. You'd think that Google would make Chrome funtion better for Linux users, since Chrome OS is Linux-based.

Definately a big "thanks" to Google...

Reply Parent Score: 5