The only allowed plug-ins are the ones mentioned in the blog post. Installed extensions that require NPAPI plugins will no longer be able to load those plugins. In September 2015 (Chrome 45) we will remove the override and NPAPI support will be permanently removed from Chrome.
EnabledPlugins, PluginsAllowedForUrls) will temporarily re-enable NPAPI.
In addition, setting any of the plugin Enterprise policies (e.g. We will provide an override for advanced users (via chrome://flags/#enable-npapi) and enterprises (via Enterprise Policy) to temporarily re-enable NPAPI (via the page action UI ) while they wait for mission-critical plugins to make the transition. 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. All NPAPI plugins will appear as if they are not installed, as they will not appear in the ugins list nor will they be instantiated (even as a placeholder). In April 2015 (Chrome 42) NPAPI support will be disabled by default in Chrome and we will unpublish extensions requiring NPAPI plugins from the Chrome Web Store.
