Closed
Bug 110870
Opened 23 years ago
Closed 23 years ago
[RFE] Load Java Plugin from Default Install Directory
Categories
(Core Graveyard :: Plug-ins, enhancement)
Tracking
(Not tracked)
People
(Reporter: ariel_gonz, Assigned: serhunt)
Details
I think it would be a good idea if instead of having to copy or install Java
spesifically for the browser, if the plugin could be loaded from the default
install path.
I don't know the JRE installer works for other Operating Systems, but for
Windows its in the normal C:\Program Files\Javasoft etc directory. It could be
loaded from there instead of copying to the plugins directory in mozilla.
This would help greatly on upgrades, since ideally you would just delete your
whole mozilla directory and decompress the new ones (like I do for nightlies).
If possible, this could also extend to other plugins.
Comment 1•23 years ago
|
||
U won' believe this? I just asked peter if we are already doing this..and am
awaiting his response. I just tried the same thing on windows trunk (verifying
fix for bug 77231) and see that if the java plugin dll's are not in the 6.x
plugins folder, java is not recognized/picked up from the javasoft folder.
Peter, aren't we already doing this? Did this break..or was this never the case.
Pls comment, Thanks.
Comment 2•23 years ago
|
||
pref("plugin.do_JRE_Plugin_Scan",true); does the magic...Peter just reminded me
. Add this line in all.js and this works. I think there is already a bug open
for this issue.
Comment 3•23 years ago
|
||
dup of 75651 ?
*** This bug has been marked as a duplicate of 75651 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
Comment 4•23 years ago
|
||
> pref("plugin.do_JRE_Plugin_Scan",true); does the magic
It does not for me. Which Java Plug-In version does it work with? I use 1.3.0_02
on WindowsME.
Comment 5•23 years ago
|
||
Yeah.
The Java plugin is going through some change that my require us to stop
"scanning" for it and require explicit "registration". This is not final yet and
for future versions, so I havn't checked in the pref:
pref("plugin.do_JRE_Plugin_Scan",true);
But you should be able to use it now if you manually add it to all.js or
about:config.
Shrirang, can you verify this still works after recent changes, even on Windows Me?
Comment 6•23 years ago
|
||
Peter: Do you mean this pref will not work from prefs.js or user.js as
user_pref("plugin.do_JRE_Plugin_Scan",true); which would imply it's not
registered if started from user prefs files?
Comment 7•23 years ago
|
||
verif y'day on win98 that this works with the pref in "ALL.JS".
Comment 8•23 years ago
|
||
shrir: If it works only from all.js, this is no help at all as all.js is
rewritten during every installation. Adding the line to all.js is not simpler
than manually moving a few DLL files.
Comment 9•23 years ago
|
||
well, that incinvenience will be solved once Peter checks in the required
pref...till then, bear with us, I would say.
Comment 10•23 years ago
|
||
Okay, by popular demand, I'll check-in the pref as part of bug 78150.
Comment 11•22 years ago
|
||
mass duplicate verifications . For filtering purposes, pls use keywd
"massdupverification"
Status: RESOLVED → VERIFIED
Updated•2 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•