Closed Bug 175030 Opened 23 years ago Closed 22 years ago

Mozilla displays only blank page when accessing specified URL

Categories

(SeaMonkey :: General, defect)

PowerPC
Mac System 9.x
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: koloszars, Assigned: asa)

References

()

Details

Repeated attempts at accessing this page with Mozilla versions 1.2a and 1.2b yield only blank page as result. Full page content shows up for Netscape 4.79.
Paul, can you reproduce this problem using another Mozilla user profile? WorksForMe using FizzillaCFM/2002101612 on 10.1.5.
Summary: blank page only → Mozilla displays only blank page when accessing specified URL
Greg, sorry but I am new at this. How do I go about looking at the page with another Mozilla user profile?
Launch the Mozilla Profile Manager file rather than the Mozilla application.
Okay, works in another profile. I believe I have traced the problem down to the old prefs.js file. Any thoughts on how I might fix that? I haven't been able to get at mail accounts when I make the new profile. Sure, I can recreate the basic account information, but don't know how to get at the old mail.
Paul, it's of more interest to us to determine what, if anything, in your old profile is wrong rather than getting it working again. It's a bug report, not technical support. Try deleting the cache folder from the old profile and test again (using the old profile).
Apologies. I thought the seemingly corrupted prefs.js was the problem, as I could replicate the problem in a new profile when I transferred the prefs.js file to new profile. Guess I should have mentioned that. Sorry. Deleted cache. Still no homedepot.com.
WFM in build 2002102814 PC/Win98. If it is working in a new profile per comment 4, this is not a TE bug.
Assignee: momoi → asa
Component: The Americas → Browser-General
Product: Tech Evangelism → Browser
QA Contact: jonrubin → asa
Version: unspecified → other
Paul, glad your new profile is working. If you still have that old corrupt prefs.js file, you could attach it to this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.