Closed Bug 28037 Opened 25 years ago Closed 25 years ago

Java becomes disabled after adding a profile

Categories

(Core Graveyard :: Java: OJI, defect, P3)

x86
Windows NT
defect

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 27462

People

(Reporter: pawyskoczka, Assigned: drapeau)

References

()

Details

(Whiteboard: [PDT+])

Build is 2000021516
Platform is Windows NT
New JRE 1.3 is installed

Steps to reproduce:
1. Delete the mozregistry.dat and user50 folder
2. Install Seamonkey - Typical
3. After the installation, the profile manager is displayed
3a. Accept the default profile and then the browser is launched.
4. Go to http://www.javasoft.com, Java is disabled
5. Close the browser
6. Restart the browser and go to http://www.javasoft.com, now Java is enabled
7. Start the browser in the Dos window using mozilla -ProfileWizard
8. Now create a new profile and launch the browser
9. Go to http://www.javasoft.com and java is not enabled
10. From mow on java will never be enabled, not matter what profile you use.
Keywords: beta1
Putting on PDT+ radar for beta1.
Whiteboard: [PDT+]
Is this bug dependent on, or the same as, 27462?
This is similar but I am not using a debug verson of Seamonkey.
From Stanley's description, which I haven't been able to test since I don't have
a working JPI, it looks like any time you use the profile manager and go
straight into mozilla without restarting, Java won't work.



*** This bug has been marked as a duplicate of 27462 ***
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Verified in build 2000030609.
Status: RESOLVED → VERIFIED
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.