# Older version of Chrome

**URL:** <https://boards.straightdope.com/t/older-version-of-chrome/718235>\
**Category:** Factual Questions\
**Created:** [April 21, 2015, 11:48pm UTC](https://boards.straightdope.com/t/older-version-of-chrome/718235 "2015-04-21T23:48:06Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![dauerbach](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@dauerbach](https://boards.straightdope.com/u/dauerbach)\
**Post date:** [April 21, 2015, 11:48pm UTC](https://boards.straightdope.com/t/older-version-of-chrome/718235/1 "2015-04-21T23:48:06Z")

</div>

So, I evidently ended up with the newest version of Chrome, as proven by the fact that the one web site I need, and which uses Java, is no longer functional. Is there a) a method to make Chrome 42 work with Java or b) download and use an older version of Chrome?

---

<div class="post-metadata">

**Author:** ![engineer\_comp\_geek](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/engineer_comp_geek/32/504_2.png) [@engineer\_comp\_geek](https://boards.straightdope.com/u/engineer_comp_geek)\
**Post date:** [April 22, 2015, 12:16am UTC](https://boards.straightdope.com/t/older-version-of-chrome/718235/2 "2015-04-22T00:16:21Z")

</div>

There’s a flag called //flags/#enable-npapi you can set to make it work (for now).

> [@](#):
>
> 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. All NPAPI plugins will appear as if they are not installed, as they will not appear in the navigator.plugins list nor will they be instantiated (even as a placeholder). 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 (via the page action UI) while they wait for mission-critical plugins to make the transition. In addition, setting any of the plugin Enterprise policies (e.g. EnabledPlugins, PluginsAllowedForUrls) will temporarily re-enable NPAPI.

From here:  
[http://www.chromium.org/developers/npapi-deprecation](http://www.chromium.org/developers/npapi-deprecation)

---

<div class="post-metadata">

**Author:** ![dauerbach](https://avatars.discourse-cdn.com/v4/letter/d/c2a13f/32.png) [@dauerbach](https://boards.straightdope.com/u/dauerbach)\
**Post date:** [April 22, 2015, 2:01am UTC](https://boards.straightdope.com/t/older-version-of-chrome/718235/3 "2015-04-22T02:01:02Z")

</div>

Good to know, but how do I perform the over rides?

---

<div class="post-metadata">

**Author:** ![RealityChuck](https://sea3.discourse-cdn.com/straightdope/user_avatar/boards.straightdope.com/realitychuck/32/195_2.png) [@RealityChuck](https://boards.straightdope.com/u/RealityChuck)\
**Post date:** [April 22, 2015, 2:25am UTC](https://boards.straightdope.com/t/older-version-of-chrome/718235/4 "2015-04-22T02:25:17Z")

</div>

Type “Chrome://flags/#enable-npapi” in the address field and press enter. The flag will display. Click to enable. Shut down ALL instances of Chrome and it should work as soon as you reopen it.

This is only a temporary solution; Chrome will remove this flag by the end of the year. It’s a very old API (the “N” stands for “Netscape”) and Google has the right idea. Thery announced this two years ago, but Java hasn’t done anything.