Closed Bug 82255 Opened 24 years ago Closed 24 years ago

Using Netscape plugins from custom user directory

Categories

(Core Graveyard :: Plug-ins, defect)

Product:
Core Graveyard
Component:
Plug-ins
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED DUPLICATE of bug 45699

People

(Reporter: ilya.konstantinov+future, Assigned: serhunt)

Details

Often, a user might want to keep plugins installed privately in his/her home directory instead of installing them system-wide (which is not always possible) in Mozilla's installation directory. Netscape Navigator 4 allowed placing plugins in ~/.netscape/plugins/, but Mozilla doesn't seem to allow a similar thing. There's an undocumented environment variable - NS600_PLUGIN_PATH - which can point Mozilla to an additional directory of plugins (so you can point it to your old ~/.netscape/plugins and have the old plugins back). I think this environment variable should be documented, or better yet, it should be implemented via the GUI.
=>plugins
Assignee: asa → av
Component: Browser-General → Plug-ins
QA Contact: doronr → shrir
*** This bug has been marked as a duplicate of 45699 ***
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → DUPLICATE
mass duplicate verifications . For filtering purposes, pls use keywd "massdupverification"
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.