plugin.expose_full_path - Doesn't on Nightly?

[KarmaQ]

Apologies if I missed this, it's not something I use very often. Has plugin.expose_full_path been removed form nightly, as setting this to true has no effect, although it works in 18.x Tried this on a fresh install and profile.

[JayhawksRock]

I can confirm that pref has no effect. The code must be be gone or there may be some trick in dealing with click to play or another of the dozen of so prefs for plugins. IIRC exposing the path was considered to be a security risk

[pal-moz]

Bug 835969 - about:plugins no longer shows the full path when plugin.expose_full_path true is set

[Are You A Wiiizard?]

Maybe they are working on a way to show it without posing a security risk? I assume Chrome is able to do so (since they show it by default) and tbh it's such a pain not knowing where the plugin is located and then having to turn on a pref then off again...

[ffextensionguru]

In regards to comment #2 on the bug "This option exposes the full path of the plugin to web content, but gets used for troubleshooting here." Why does it expose the path to web content? Was there a reason it should, as I would think this information is really only needed locally. Just used that particular option a couple weeks ago during the 'Java Scare' to get rid of the Java plugins on this machine since I didn't need Java on this machine.