845929 - "Always activate plugins" does not work for file:// URLS

Status: RESOLVED DUPLICATE of bug 836730

(Firefox :: Untriaged, defect)

Description

[wearyofallthiscrap]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0
Build ID: 20130215130331

Steps to reproduce:

Running FF 19.0 and using JRE 7u15 (plugin reports itself as 10.15.2.3) and loading a local, fully signed applet, from a page on a local drive, i.e.,
"file:///C:/some/path/to/page.html"
and getting the usual insecure plugin warning.  Okay, that's expected.

Following the instructions at
https://support.mozilla.org/en-US/kb/why-do-i-have-click-activate-plugins#w_how-to-always-activate-a-plugin-for-a-trusted-website
I clicked the little red Lego brick, chose "always activate plugins for this site", and went on with my work in the running Java applet.


Actual results:

When opening the same local page afterwards, I still get the same insecure warning.


Expected results:

Having chosen "always activate for this site", I expect plugins to always be activated.  :-)

This may be related to "bug 204285 - file:// URLs cannot have popups unblocked", although much of the problem there was that there's no way of knowing from the UI that you can type "<file>" into the popup exceptions dialog.

Trying further, I pulled up about:permissions, and for All Sites, changed Plugins to Allow.  (This is an isolated computer at work, I'm not worried.)  Still got the warning for file:// URLs.

Getting desperate, I changed Plugins to Always Ask, which then enabled the Plugins setting on each stored website.  There *happened* to already be a <file> website in the list, as a result of the workaround for #204285 (comment 51 there), so that let me change *its* Plugins dropdown to Allow.  That, and only that, is functioning as a workaround, but now I get the plugin warning on other sites.