Closed
Bug 183243
Opened 22 years ago
Closed 22 years ago
Random web pages do not display contents
Categories
(SeaMonkey :: General, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 139053
People
(Reporter: mark-graber, Assigned: asa)
References
()
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0) WebWasher 3.0 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.2.1) Gecko/20021130 I am not able to get www.google.com to display using Mozilla. Also not able to get past the bug report sign in using Mozilla (am using IE (gasp)) to report this. Same problem when I signed on to MD-consult (www.mdconsult.com). After sign in was complete, the main page did not display Alternatively, yahoo, cnn, espn, cd-now and amazon did display during the same session. I tried google several times in different sessions including rebooting the machine without any luck displaying the page. Reproducible: Always Steps to Reproduce: 1.just try to load www.google.com 2. 3. Actual Results: Nothing diplays but "done" is displayed at the bottom of the browser. Actually got same problem on www.mozilla.org/start/. The text in the main frame did not display. This was intermitent, though. Expected Results: Display the window properly.
From mail with reporter (who also deleted cache) --- -occurs whether or not I am running a proxy (e.g. webwasher). I did try -changing the protocol to 1.0 default when I am running a proxy but no help...... Still no display on www.google.com and some other sites. You could try following a couple of link from the CNN site (www.cnn.com). I followed the link to the info on Iraq and did not get a display except for the frame on the left side of the screen. I tried this both dial up (from home) and using a direct ethernet from work. Ran it without any proxy server but same result. More info: I think the problem is that for some sites mozilla doesn't play well with Zone Alarm Pro (firewall, available for free at www.zonelabs.com). If I turn off the firewall, things work OK...... I did give Zone Alarm permission to allow Mozilla free access to the web. Thanks for the interest. (Note: am running another build 1.2 on another machine with zone alarm and no problems. It seems to be in the 1.21 build).
Mark - which version of ZoneAlarm are you running? From bug 144223 comment 4: "It's only necessary to turn off "Privacy" for mozilla.exe in the program list. That "privacy" feature blocks ads and "cookies from tracking sites", as stated in the firewall's help files. " Similar frmo bug 139053 comment 11: "I can confirm that Mozilla 1.0 RC 2 + (and Netscape 7.0 PR 1) do not work at all when Zone Alarm Pro has ad blocking + script blocking (i.e. Privacy Control) enabled. Turning Privacy Control off in Zone Alarm Pro lets Mozilla access websites." Can you check if modifying that setting change anything?
Reporter mailed: ---------------- Hi, yes. Allowing "moblie code" to run in zone alarm alarm fixed the problem. I can also fix the problem by running through a proxy (127.0.0.1 8080) setting the proxy manually and running webwasher. EIther will allow things to display properly. THe whole problem was with the display only. Mozilla connected OK either directly or through a proxy. WHat is really strange is that after I installed the most recent release of mozilla, the same problem showed up in IE. I am not sure if mozilla set something on my computer that didn't uninstall when I tried to uninstall mozilla. Of course, I reinstalled mozilla after this test........ Thanks. Hope this isn't too much of a headache. Mark -------------- Resolving as dup of bug 139053 *** This bug has been marked as a duplicate of 139053 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Verifying as well. Reporter (who earlyer was using ZoneAlarm Pro version 3.1.395) mailed: "Problem solved with upgrade to Zone Alarm v. 3.5 Don't ask me why but it fixed it". (Thanks for the follow-up, Mark!)
Status: RESOLVED → VERIFIED
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•